---
title: "UploadPart"
slug: "storage-objectstorage-uploadpart"
updated: 2026-09-17T10:12:27Z
published: 2026-09-17T10:12:27Z
canonical: "api.ncloud-docs.com/storage-objectstorage-uploadpart"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://api.ncloud-docs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# UploadPart

Available in Classic and VPC

You can run a multipart upload, which divides an object into parts and uploads them. All parts can be uploaded one by one sequentially or all at once in parallel, but they must be numbered. Parts must be between 5 MB and 5 GB in size each, with a maximum of 10,000 allowed.

              Caution

              

If you don't complete the multipart upload, the remaining files remain in the bucket and count against your bucket capacity and are billed. Delete incomplete multipart objects to avoid unnecessary charges.

- Turn on notifications for incomplete multipart objects through the Cloud Advisor service. For more information about the Cloud Advisor service, see the [Cloud Advisor Service User Guide](https://guide.ncloud-docs.com/docs/en/cloudadvisor-overview).
- You can use the API to view and delete incomplete multipart objects.
  - View canceled or incomplete multipart uploads: [ListMultipartUploads API Guide](/docs/en/storage-objectstorage-listmultipartuploads)
  - Delete multipart: [AbortMultipartUpload API Guide](/docs/en/storage-objectstorage-abortmultipartupload)

## Requests

The following describes the request format for the endpoint. The request format is as follows.

| Method | URI |
| --- | --- |
| PUT | /{bucket-name}/{object-name} |

### Request syntax

The request syntax is as follows.

```
PUT https://{endpoint}/{bucket-name}/{object-name}?partNumber={sequential-integer}&uploadId={uploadId} # path style
PUT https://{bucket-name}.{endpoint}/{object-name}?partNumber={sequential-integer}&uploadId={uploadId} # virtual host style
```

### Request headers

For headers common to all Object Storage APIs, see [Object Storage common headers](/docs/en/storage-objectstorage#%EA%B3%B5%ED%86%B5-%EC%9A%94%EC%B2%AD-%ED%97%A4%EB%8D%94).

### Request path parameters

The following describes the parameters.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `bucket-name` | String | Required | Name of the bucket where the object is stored |
| `object-name` | String | Required | Name of the object to run the multipart upload on |

### Request query parameters

The following describes the parameters.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `partNumber` | Integer | Required | Order number to assign to the part |
| `uploadId` | String | Required | Upload ID received by running the InitiateMultipartUpload API |

### Request example

The following is a sample request.

```
PUT /some-bucket/multipart-object-123?partNumber=1&uploadId=0000015a-df89-51d0-2790-dee1ac994053 HTTP/1.1
Authorization: {authorization-string}
x-amz-date: 20170318T035641Z
Content-Type: application/pdf
Host: kr.object.ncloudstorage.com
Content-Length: 13374550
```

## Responses

The following describes the response format.

### Response headers

For response headers common to all Object Storage APIs, see [Object Storage common response headers](/docs/en/storage-objectstorage#%EA%B3%B5%ED%86%B5%EC%9D%91%EB%8B%B5%ED%97%A4%EB%8D%94).

### Response status codes

For response status codes common to all Object Storage APIs, see [Object Storage response status codes](/docs/en/storage-objectstorage#%EC%98%A4%EB%A5%98%EC%BD%94%EB%93%9C).

### Response example

The following is a sample response.

```
HTTP/1.1 200 OK
Date: Sat, 18 Mar 2017 03:56:41 GMT
Accept-Ranges: bytes
ETag: "7417ca8d45a71b692168f0419c17fe2f"
Content-Length: 0
```