Docs

Torch Object Storage

Working with objects

Uploading objects

When you upload a file to TOS, it is stored as a TOS object. This topic explains how to upload an object to the TOS console.

Notes

Before uploading any objects, make sure you have created a bucket. For more information, see Creating buckets.

For object naming rules, see Object.

You can use the console to upload an object up to 5 GiB. For objects larger than 5 GiB, use the API, which allows you to upload up to 48.8 TiB using the multipart method. Each part can be up to 5 GiB, and you can upload up to 10,000 parts, for a total of 48.8 TiB. For instructions, see UploadPart.

By default, the owner of an account has full permissions. IAM users have no permissions by default. If an IAM user needs to perform this operation, the account owner must grant the user the tos:PutObject permission using an IAM or bucket policy.

Steps

In the left navigation pane, click Buckets.

In the top menu bar, select the project of the bucket you want to manage.

In the Buckets list, click the bucket you want to manage.

On the Objects page, click Upload file. On the Upload file page, set the parameters.

Parameter	Description
Upload to	Specify the storage path in the TOS bucket to which the object will be uploaded. Current Directory: Uploads the object to the current directory. Specified Directory: Customizes the directory name and upload the object to this directory. When naming the directory, be aware of the following: Directory names can contain Chinese characters, letters, numbers, and common symbols. You can use forward slashes (/) to quickly create subfolders. However, the folder name cannot start with a forward slash (/) or backslash (\) and cannot contain consecutive forward slashes (/). .. cannot be used as a folder name.
To be uploaded	Select or drag and drop files or folders from your local device. tip You cannot have duplicate filenames in the same bucket. If you upload a file with the same name as an existing file, the system will process it according to the following rules: If versioning is disabled: The uploaded file will replace the existing file. If versioning is enabled: The uploaded file will become the latest version, and the existing file will be kept as a previous version. For more information, see Versioning.
Advanced settings	Storage type	Expand Advanced settings to specify the storage type for the object to be uploaded. By default, objects use the storage type of the bucket they are stored in. The options are as follows: Inherit Bucket (Default): Objects use the storage type of the bucket they are stored in. Standard Storage: High availability, reliability, and performance, suitable for frequently accessed data. Intelligent Tiering: Designed for data with unpredictable access patterns, which will incur object monitoring charges. For more information, see Intelligent Tiering. Infrequent Access Storage: Designed for frequently accessed data with a minimum storage duration of 30 days. Flashback Archive: Optimized for rarely accessed data with a minimum storage duration of 90 days. Archive: Suited for long-term storage of rarely accessed data with a minimum storage duration of 90 days. You need to restore data in Archive before reading them. Cold Archive: Suited for long-lived, rarely accessed data with flexible latency requirements. The minimum storage duration is 180 days. You need to restore data in Cold Archive before reading them. Deep Cold Archive: Cost-effective storage for extremely cold data with ultra-long retention needs. The minimum storage duration is 180 days. You need to restore data in Deep Cold Archive before reading them. tip Cold Archive is only supported in China (Beijing), China (Shanghai), and China (Guangzhou). Deep Cold Archive is only supported in China (Beijing), China (Shanghai), and China (Guangzhou). Deep Cold Archive is currently in closed beta. Please contact your account manager for access. For more information, see Storage type. If you have enabled multi-AZ redundancy for the bucket, you can only choose the storage type from the following options: Inherit Bucket, Standard Storage (Multi-AZ), Intelligent Tiering (Multi-AZ), Infrequent Access Storage (Multi-AZ), and Flashback Archive (Multi-AZ). For more information on multi-AZ, see Multi-AZ redundancy. For detailed information about storage types, please refer to .
		Server-Side encryption	Expand Advanced settings to configure the server-side encryption method. The available encryption options are: Inherit Bucket Encryption Configuration (Default): An object gets the server-side encryption method from its bucket. You can find the server-side encryption method of the bucket in the Basic information section of the bucket's Overview page. You can also change the bucket's server-side encryption method. For instructions, see Setting bucket encryption. None: No encryption applied. SSE-TOS: TOS-managed encryption. Objects are encrypted automatically upon upload and decrypted during download using TOS-hosted keys. For more information, see Server-side encryption. SSE-KMS: Uses keys managed by Volcano Engine's Key Management Service (KMS) to encrypt and decrypt objects. For more information, see Server-side encryption. tip SSE-TOS and SSE-KMS are only supported in China (Beijing), China (Shanghai), Asia Pacific (Johor), and Asia Pacific (Jakarta). You can only set the server-side encryption method when uploading objects. You cannot change the encryption settings of uploaded objects. If you are using SSE-KMS for server-side encryption for the first time, you must first activate KMS. Although activating KMS is free, using the service incurs charges. Using SSE-KMS for server-side encryption generates API call fees, and creating KMS keys generates key management fees. These fees are charged by KMS. For more information, see KMS Billing Overview.
		Encryption algorithm	Expand Advanced settings and select the encryption algorithm for the key. Options include AES256 and SM4. tip The encryption algorithm parameter only appears when SSE-KMS or SSE-TOS is selected for Server-Side encryption. The AES-256 algorithm is only supported in China (Beijing), China (Shanghai), Asia Pacific (Johor), and Asia Pacific (Jakarta). The SM4 algorithm is only supported in China (Beijing) and China (Shanghai).
		Encryption Key Type	Expand Advanced settings to set the encryption key. The default setting is Custom Key. tip The Encryption Key Type parameter only appears when SSE-KMS is selected for Server-Side encryption.
		Custom Key	Expand Advanced settings and select a key created in KMS. If you have not created a key yet, proceed to the KMS console to do so. For instructions, see KMS Quickstarts. tip The Encryption Key Type parameter only appears when SSE-KMS is selected for Server-Side encryption.
		Metadata	Expand Advanced settings and click Add Field to configure object metadata. For more information on user-defined object metadata, see Managing object metadata.
		Access permission	The following options are available when setting the access control list (ACL) policy for objects to be uploaded to the bucket: Inherit bucket: An object inherits the permissions from its bucket, meaning the object's ACL will mirror the bucket's. For details on the relationship between object ACL and bucket ACL, see Inheriting ACL settings from the bucket. tip To allow newly uploaded objects to automatically adopt the bucket's ACL policy, turn on the Object ACL default policy switch. For instructions, see Enabling objects to automatically apply bucket ACL. Private (Default): Only the object owner and authorized accounts have read and write permissions. This is the recommended setting. Public read: All users, including those making anonymous requests, can read the object. However, only the owner and authorized accounts can modify it. Public read/write: All users, including those making anonymous requests, can have full read and write access to the object.

tip

After setting the parameters and adding the files, you can view the list of files that will be uploaded on the Upload file page.

To cancel the upload of a selected file, click Remove in the Actions column. To cancel the upload of all files, click Clear list above the file list.

Do not refresh or close the page while uploading. Otherwise, the upload task will be interrupted and the list will be cleared.

Verify the files you want to upload, and click Upload.

Then, you are redirected to the Task progress management page. To view task progress and status, you can also click Task center in the upper-right corner of the console.

Other operations

To view the upload progress and status, go to the Upload task tab in the Task progress management panel. From this tab, you can also perform the following actions:

Cancel upload: In the task list, click Cancel in the Actions column of the task you want to cancel.

Re-upload: If an upload task is canceled or fails, click Retry in the Actions column of the task.

Clear upload record: In the task list, click Remove in the Actions column of the task to clear its record. Note that deleting the record does not delete the uploaded object.

Copy link: In the task list, click on the desired task name. Then, click Copy Link in the Actions column of the object to copy its download link.

Clear successful tasks: At the top left of the task list, click Clear successful tasks to remove all records of successfully uploaded objects.

Last updated: 2026.02.11 11:21:41