This page shows you how to compose Cloud Storage objects into a single object. A compose request takes between 1 and 32 objects and creates a new, composite object. The composite object is a concatenation of the source objects in the order they were specified in the request.
Note the following when composing objects:
- The source objects are unaffected by the composition process. If they are meant to be temporary, you must delete them once you've successfully completed the composition.
- Because other storage classes are subject to early deletion fees, you should always use Standard storage for temporary objects.
- Frequent deletions associated with compose can increase your storage bill significantly if your bucket has data protection features enabled. Consider disabling soft delete on buckets with high rates of compose operations. With Object Versioning, specify the object versions when deleting source objects to permanently delete them and avoid their becoming noncurrent objects.
Required roles
To get the permissions that you need to compose objects, 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 compose objects. To see the exact permissions that are
required, expand the Required permissions section:
Required permissions
- storage.objects.create
- storage.objects.delete- This permission is only required if you want to give the object you compose the same name as an object that already exists in the bucket.
 
- storage.objects.get
- storage.objects.list- This permission is only required if you want to use wildcards to compose objects with a common prefix without having to list each object separately in your Google Cloud CLI command.
 
If you want to set a retention configuration for the object
you compose, you'll also need the storage.objects.setRetention permission. To
get this permission, ask your administrator to grant you the Storage Object
Admin (roles/storage.objectAdmin) role instead of the Storage Object User
(roles/storage.objectUser) role.
You can also get these permissions with other predefined roles or custom roles.
For information about granting roles on buckets, see Set and manage IAM policies on buckets.
Create a composite object
Command line
Use the gcloud storage objects compose command:
gcloud storage objects compose gs://BUCKET_NAME/SOURCE_OBJECT_1 gs://BUCKET_NAME/SOURCE_OBJECT_2 gs://BUCKET_NAME/COMPOSITE_OBJECT_NAME
Where:
- BUCKET_NAMEis the name of the bucket that contains the source objects.
- SOURCE_OBJECT_1and- SOURCE_OBJECT_2are the names of the source objects to use in the object composition.
- COMPOSITE_OBJECT_NAMEis the name you are giving to the result of the object composition.
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 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.
      
     
      
      
  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.
      
     
      
      
  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.
      
     
      
      
  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.
      
    C++
  
  
    
    C#
  
  
    
    Go
  
  
    
    Java
  
  
    
    Node.js
  
  
    
    PHP
  
  
    
    Python
  
  
    
    Ruby
  
  
    
    
REST APIs
JSON API
- Have gcloud CLI installed and initialized, which lets you generate an access token for the - Authorizationheader.
- Create a JSON file that contains the following information: - { "sourceObjects": [ { "name": "SOURCE_OBJECT_1" }, { "name": "SOURCE_OBJECT_2" } ], "destination": { "contentType": "COMPOSITE_OBJECT_CONTENT_TYPE" } } - Where: - SOURCE_OBJECT_1and- SOURCE_OBJECT_2are the names of the source objects to use in the object composition.
- COMPOSITE_OBJECT_CONTENT_TYPEis the Content-Type of the resulting composite object.
 
- Use - cURLto call the JSON API with a- POSTObject request:- curl -X POST --data-binary @JSON_FILE_NAME \ -H "Authorization: Bearer $(gcloud auth print-access-token)" \ -H "Content-Type: application/json" \ "https://storage.googleapis.com/storage/v1/b/BUCKET_NAME/o/COMPOSITE_OBJECT_NAME/compose" - Where: - JSON_FILE_NAMEis the name of the file you created in the previous step.
- BUCKET_NAMEis the name of the bucket that contains the source objects.
- COMPOSITE_OBJECT_NAMEis the name you are giving to the result of the object composition.
 
If successful, the response is an object resource for the resulting composite object.
XML API
- Have gcloud CLI installed and initialized, which lets you generate an access token for the - Authorizationheader.
- Create an XML file that contains the following information: - <ComposeRequest> <Component> <Name>SOURCE_OBJECT_1</Name> </Component> <Component> <Name>SOURCE_OBJECT_2</Name> </Component> </ComposeRequest> - Where: - SOURCE_OBJECT_1and- SOURCE_OBJECT_2are the names of the source objects to use in the object composition.
 
- Use - cURLto call the XML API with a- PUTObject request that includes the- composequery string parameter:- curl -X PUT --data-binary @XML_FILE_NAME \ -H "Authorization: Bearer $(gcloud auth print-access-token)" \ -H "Content-Type: COMPOSITE_OBJECT_CONTENT_TYPE" \ "https://storage.googleapis.com/BUCKET_NAME/COMPOSITE_OBJECT_NAME?compose" - Where: - XML_FILE_NAMEis the name of the file you created in the previous step.
- COMPOSITE_OBJECT_CONTENT_TYPEis the Content-Type of the resulting composite object.
- BUCKET_NAMEis the name of the bucket that contains the source objects.
- COMPOSITE_OBJECT_NAMEis the name you are giving to the result of the object composition.
 
If successful, an empty response body is returned.
What's next
- Learn more about object composition.
- Learn how to use request preconditions to prevent race conditions.