Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://cloud.google.com/storage/docs/json_api/v1/how-tos/multipart-upload below:

Upload objects from a file system | Cloud Storage

• Discover

• Product overview
• Storage Intelligence overview

• Get started

• Terraform support for Cloud Storage
• Configure and manage Storage Intelligence

• Create buckets

• Create a bucket
• Domain-named bucket verification

• Access and manage buckets

• List buckets
• Change the default storage class of a bucket
• Move and rename buckets
• Delete buckets

• Upload and download objects

• About objects
• Overview of uploads and downloads

• Access and manage objects

• List objects
• Copy, rename, and move objects
• Change an object's storage class
• Tools to access and manage objects using a directory structure
• Object transcoding
• Delete objects

• Get insights on your stored data

• Analyze stored data with Gemini Cloud Assist

• Cache objects

• About caching

• Control data lifecycles

• Options for controlling data lifecycles

• Make requests

• Consistency in Cloud Storage operations
• Batched requests
• Use long-running operations
• Paginate results
• URI wildcards

• Secure data

• Monitor data and usage

• Use Cloud Audit Logs with Cloud Storage
• Usage logs and storage logs
• Use Cloud Audit Logs with storage batch operations
• Use Cloud Logs with storage batch operations
• Use Cloud Audit Logs with Storage Insights
• Use gRPC client-side metrics
• Use client-side traces

• Protection, backup, and recovery

• Overview

• Mount buckets with Cloud Storage FUSE

• Overview
• Quickstart
• Install Cloud Storage FUSE
• Mount buckets

• Work across products, Clouds, and platforms

• Best practices for media workloads
• Interoperability
• Use Cloud Storage with Big Data
• Integration with Google Cloud Platform services and tools

• Troubleshoot

• Troubleshooting

• AI and ML
• Application development
• Application hosting
• Compute
• Data analytics and pipelines
• Databases
• Distributed, hybrid, and multicloud
• Generative AI
• Industry solutions
• Networking
• Observability and monitoring
• Security
• Storage

• Access and resources management
• Costs and usage management
• Google Cloud SDK, languages, frameworks, and tools
• Infrastructure as code
• Migration

• Google Cloud Home
• Free Trial and Free Tier
• Architecture Center
• Blog
• Contact Sales
• Google Cloud Developer Center
• Google Developer Center
• Google Cloud Marketplace
• Google Cloud Marketplace Documentation
• Google Cloud Skills Boost
• Google Cloud Solution Center
• Google Cloud Support
• Google Cloud Tech Youtube Channel

Stay organized with collections Save and categorize content based on your preferences.

This page shows you how to upload objects to your Cloud Storage bucket from your local file system. An uploaded object consists of the data you want to store along with any associated metadata. For a conceptual overview, including how to choose the optimal upload method based on your file size, see Uploads and downloads.

For instructions on uploading from memory, see Upload objects from memory.

To get the permissions that you need to upload objects to a bucket, ask your administrator to grant you the Storage Object User (roles/storage.objectUser) IAM role on the bucket. This predefined role contains the permissions required to upload an object to a bucket. To see the exact permissions that are required, expand the Required permissions section:

• storage.objects.create
• storage.objects.delete
  • This permission is only required for uploads that overwrite an existing object.
• storage.objects.get
  • This permission is only required if you plan on using the Google Cloud CLI to perform the tasks on this page.
• storage.objects.list
  • This permission is only required if you plan on using the Google Cloud CLI to perform the tasks on this page. This permission is also required if you want to use the Google Cloud console to verify the objects you've uploaded.

If you plan on using the Google Cloud console to perform the tasks on this page, you'll also need the storage.buckets.list permission, which is not included in the Storage Object User (roles/storage.objectUser) role. To get this permission, ask your administrator to grant you the Storage Admin (roles/storage.admin) role on the project.

You can also get these permissions with other predefined roles or custom roles.

For information about granting roles on buckets, see Use IAM with buckets.

Complete the following steps to upload an object to a bucket:

1. In the Google Cloud console, go to the Cloud Storage Buckets page.

   Go to Buckets

2. In the list of buckets, click the name of the bucket that you want to upload an object to.

3. In the Objects tab for the bucket, either:

   • Drag files from your desktop or file manager to the main pane in the Google Cloud console.

   • Click Upload > Upload files, select the files you want to upload in the dialog that appears, then click Open.

   Note: If you are using the Chrome browser, folder uploads are also supported.

To learn how to get detailed error information about failed Cloud Storage operations in the Google Cloud console, see Troubleshooting.

Use the gcloud storage cp command:

gcloud storage cp OBJECT_LOCATION gs://DESTINATION_BUCKET_NAME

Where:

• OBJECT_LOCATION is the local path to your object. For example, Desktop/dog.png.

• DESTINATION_BUCKET_NAME is the name of the bucket to which you are uploading your object. For example, my-bucket.

If successful, the response looks like the following example:

Completed files 1/1 | 164.3kiB/164.3kiB

You can set fixed-key and custom object metadata as part of your object upload by using command flags.

For more information, see the Cloud Storage C++ API reference documentation.

To authenticate to Cloud Storage, set up Application Default Credentials. For more information, see Set up authentication for client libraries.

For more information, see the Cloud Storage C# API reference documentation.

To authenticate to Cloud Storage, set up Application Default Credentials. For more information, see Set up authentication for client libraries.

For more information, see the Cloud Storage Go API reference documentation.

To authenticate to Cloud Storage, set up Application Default Credentials. For more information, see Set up authentication for client libraries.

For more information, see the Cloud Storage Java API reference documentation.

To authenticate to Cloud Storage, set up Application Default Credentials. For more information, see Set up authentication for client libraries.

The following sample uploads an individual object:

The following sample uploads multiple objects concurrently:

The following sample uploads all objects with a common prefix concurrently:

For more information, see the Cloud Storage Node.js API reference documentation.

To authenticate to Cloud Storage, set up Application Default Credentials. For more information, see Set up authentication for client libraries.

The following sample uploads an individual object:

The following sample uploads multiple objects concurrently:

The following sample uploads all objects with a common prefix concurrently:

For more information, see the Cloud Storage PHP API reference documentation.

To authenticate to Cloud Storage, set up Application Default Credentials. For more information, see Set up authentication for client libraries.

For more information, see the Cloud Storage Python API reference documentation.

To authenticate to Cloud Storage, set up Application Default Credentials. For more information, see Set up authentication for client libraries.

The following sample uploads an individual object:

The following sample uploads multiple objects concurrently:

The following sample uploads all objects with a common prefix concurrently:

For more information, see the Cloud Storage Ruby API reference documentation.

To authenticate to Cloud Storage, set up Application Default Credentials. For more information, see Set up authentication for client libraries.

You can use a Terraform resource to upload an object. Either content or source must be specified.

The JSON API distinguishes between media uploads, in which only object data is included in the request, and JSON API multipart uploads, in which both object data and object metadata are included in the request.

1. Have gcloud CLI installed and initialized, which lets you generate an access token for the Authorization header.

2. Use cURL to call the JSON API with a POST Object request:

   curl -X POST --data-binary @OBJECT_LOCATION \
       -H "Authorization: Bearer $(gcloud auth print-access-token)" \
       -H "Content-Type: OBJECT_CONTENT_TYPE" \
       "https://storage.googleapis.com/upload/storage/v1/b/BUCKET_NAME/o?uploadType=media&name=OBJECT_NAME"

   Where:

   • OBJECT_LOCATION is the local path to your object. For example, Desktop/dog.png.
   • OBJECT_CONTENT_TYPE is the content type of the object. For example, image/png.
   • BUCKET_NAME is the name of the bucket to which you are uploading your object. For example, my-bucket.
   • OBJECT_NAME is the URL-encoded name you want to give your object. For example, pets/dog.png, URL-encoded as pets%2Fdog.png.

1. Have gcloud CLI installed and initialized, which lets you generate an access token for the Authorization header.

2. Create a multipart/related file that contains the following information:

   --BOUNDARY_STRING
   Content-Type: application/json; charset=UTF-8
   
   OBJECT_METADATA
   
   --BOUNDARY_STRING
   Content-Type: OBJECT_CONTENT_TYPE
   
   OBJECT_DATA
   --BOUNDARY_STRING--

   Where:

   • BOUNDARY_STRING is a string you define that identifies the different parts of the multipart file. For example, separator_string.
   • OBJECT_METADATA is metadata you want to include for the file, in JSON format. At a minimum, this section should include a name attribute for the object, for example {"name": "myObject"}.
   • OBJECT_CONTENT_TYPE is the content type of the object. For example, text/plain.
   • OBJECT_DATA is the data for the object.

   For example:

   --separator_string
   Content-Type: application/json; charset=UTF-8
   
   {"name":"my-document.txt"}
   
   --separator_string
   Content-Type: text/plain
   
   This is a text file.
   --separator_string--

3. Use cURL to call the JSON API with a POST Object request:

   curl -X POST --data-binary @MULTIPART_FILE_LOCATION \
       -H "Authorization: Bearer $(gcloud auth print-access-token)" \
       -H "Content-Type: multipart/related; boundary=BOUNDARY_STRING" \
       -H "Content-Length: MULTIPART_FILE_SIZE" \
       "https://storage.googleapis.com/upload/storage/v1/b/BUCKET_NAME/o?uploadType=multipart"

   Where:

   • MULTIPART_FILE_LOCATION is the local path to the multipart file you created in step 2. For example, Desktop/my-upload.multipart.
   • BOUNDARY_STRING is the boundary string you defined in Step 2. For example, my-boundary.
   • MULTIPART_FILE_SIZE is the total size, in bytes, of the multipart file you created in Step 2. For example, 2000000.
   • BUCKET_NAME is the name of the bucket to which you are uploading your object. For example, my-bucket.

If the request succeeds, the server returns the HTTP 200 OK status code along with the file's metadata.

1. Have gcloud CLI installed and initialized, which lets you generate an access token for the Authorization header.

2. Use cURL to call the XML API with a PUT Object request:

   curl -X PUT --data-binary @OBJECT_LOCATION \
       -H "Authorization: Bearer $(gcloud auth print-access-token)" \
       -H "Content-Type: OBJECT_CONTENT_TYPE" \
       "https://storage.googleapis.com/BUCKET_NAME/OBJECT_NAME"

   Where:

   • OBJECT_LOCATION is the local path to your object. For example, Desktop/dog.png.
   • OBJECT_CONTENT_TYPE is the content type of the object. For example, image/png.
   • BUCKET_NAME is the name of the bucket to which you are uploading your object. For example, my-bucket.
   • OBJECT_NAME is the URL-encoded name you want to give your object. For example, pets/dog.png, URL-encoded as pets%2Fdog.png.

You can set additional object metadata as part of your object upload in the headers of the request in the same way the previous example sets Content-Type. When working with the XML API, metadata can only be set at the time the object is written, such as when uploading, copying, or replacing the object. For more information, see Editing object metadata.

Complete the following steps to copy the contents of a directory to a bucket:

Use the gcloud storage rsync command with the --recursive flag:

gcloud storage rsync --recursive LOCAL_DIRECTORY gs://DESTINATION_BUCKET_NAME/FOLDER_NAME

Where:

• LOCAL_DIRECTORY is the path to the directory that contains the files you want to upload as objects. For example, ~/my_directory.

• DESTINATION_BUCKET_NAME is the name of the bucket to which you want to upload objects. For example, my-bucket.

• FOLDER_NAME (optional) is the name of the folder within the bucket that you want to upload objects to. For example, my-folder.

If successful, the response looks like the following example:

Completed files 1/1 | 5.6kiB/5.6kiB

You can set fixed-key and custom object metadata as part of your object upload by using command flags.

• Learn about naming requirements for objects.
• Learn about using folders to organize your objects.
• Transfer objects from your Compute Engine instance.
• Transfer data from cloud providers or other online sources, such as URL lists.
• Control who has access to your objects and buckets.
• View your object's metadata, including the URL for the object.

If you're new to Google Cloud, create an account to evaluate how Cloud Storage performs in real-world scenarios. New customers also get $300 in free credits to run, test, and deploy workloads.

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2025-08-07 UTC.

[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-07 UTC."],[],[]]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4