Stay organized with collections Save and categorize content based on your preferences.
An Apps Script project deployment is a version of the script that is made available for use as a web app, add-on, or API executable. By creating and managing deployments, you can iterate on your code, keep track of your changes, and control the exact code version your users have access to.
There are two types of deployments:
A head deployment is the current project code. When you create an Apps Script project, you automatically create a head deployment for that project.
The head deployment is always in sync with most recently saved code. For example, if you create a versioned deployment and then modify your code, the head deployment reflects those changes, while the versioned deployment remains intact.
Use head deployments to test code. Don't use head deployments for public use.
Note: There is only ever one head deployment for each Apps Script project. To use a head deployment, you must have at least read access to the script project. Versioned deploymentsA versioned deployment makes a specific version of the project code available. This lets your users continue to use a functioning version while you make changes and improvements to the code.
When your application is published for public consumption, always use a versioned deployment. You can have multiple active versioned deployments at one time.
Important: You can't transfer ownership of versioned deployments. If you transfer ownership of a script project to someone, the owner of the existing versioned deployments within the project doesn't change. If an administrator deletes the deployment owner's account, you might experience script errors for their deployments.
Create a versioned deploymentTo deploy a version of a Google Workspace add-on, Editor add-on, Google Chat app, or an API executable, you must first switch your Apps Script’s Google Cloud project association from the default project to a standard project.
To create a versioned deployment, follow these steps:
Enter the information about your deployment and click Deploy.
Note: Each new deployment can be shared as a library. If you share the script as a library, the deployment description is visible to users of the library.To view the deployments of an Apps Script project, at the top, click Deploy > Manage deployments.
To view the code of a specific version, refer to View a previous version.
Edit a versioned deploymentYou can edit a versioned deployment to change its description or version. To edit a deployment, follow these steps:
Make your changes and click Deploy.
If you want to edit an archived deployment, you must redeploy it, then follow the preceding steps.
When you want to deploy a change to the project code, create a new version and edit the deployment to use it. The new version is automatically used by any users that use that deployment.
Every deployment has an associated string ID automatically created for it. To find this ID, follow the steps below:
Select an active deployment to find its ID.
Deployment IDs only appear on active deployments.
How you test a deployment depends on the type of app you build.
Archive a versioned deploymentYou can't delete versioned deployments. Instead, you can archive them.
To archive a versioned deployment:
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-04 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-04 UTC."],[[["Apps Script deployments make your script usable as a web app, add-on, or API executable, allowing for controlled code iteration and user access."],["Head deployments automatically reflect the latest code changes and are best suited for testing purposes, while versioned deployments offer stability for public use by linking to specific project versions."],["Versioned deployments, crucial for public applications, require switching to a standard Google Cloud Project and can be managed through the deployment settings within the Apps Script project."],["You can view, edit, and archive versioned deployments, but deletion is not possible; archived deployments can be redeployed if needed."],["Deployment IDs are essential for testing certain deployment types like Chat apps and API executables, and they can be accessed from the Manage deployments section."]]],[]]
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