Google Apps Script

Publishing to the Chrome Web Store

After you've created a web app with Google Apps Script, you can distribute it to users by publishing in the Chrome Web Store. Google Apps Script has built-in integration with the Chrome Web Store to simplify the publishing process.

  1. What is the Chrome Web Store?
  2. Preparing a script for publication
    1. Creating and deploying a web app
    2. Getting started with the Chrome Web Store
    3. Creating images for your Chrome Web Store listing
  3. Publishing a script to the Chrome Web Store
    1. Updating a published script
    2. Removing a script from the Chrome Web Store
  4. Installing a script from the Chrome Web Store

What is the Chrome Web Store?

The Chrome Web Store is an online marketplace where users can discover thousands of apps, extensions and themes for Google Chrome. To learn more, visit this page. You can publish web apps that you create with Google Apps Script in the Chrome Web Store to make it easier for users to discover them.

Preparing a script for publication

There are a few prerequisites and steps you need to complete before you publish one of your scripts in the Chrome Web Store.

Creating and deploying a web app

In order to publish a script to the Chrome Web Store, it must be a web app. A Google Apps Script web app is a script that contains a special doGet(e) function and has a user interface created with either the Html Service or the Ui Service.

After you create your web app, you must save a version of your script. To do so, choose File > Manage Versions in the Script Editor, provide a description for the version, and then click Save New Version.

Once you have saved a version of your script, you can deploy it as a web app. These instructions will guide you through the process of deploying your script as a web app.

Getting started with the Chrome Web Store

If you haven't published any items to the Chrome Web Store in the past, there are some steps you will need to take before you can publish your script.

  1. Go to the Chrome Web Store Developer Dashboard from the same account that you use for Google Apps Script. You will see a Your Listings page with an Add new item button.
  2. Click the Add new item button. Then you will see a page where you can read and accept the Google Chrome Web Store Developer Agreement. You will need to read and Accept the agreement in order to publish your scripts in the Chrome Web Store.

Creating images for your Chrome Web Store listing

When you publish a web app in the Chrome Web Store, you must supply some images: an app icon, one or more promotional images, and one or more screenshots. See Supplying Images for complete details and additional guidelines. The minimum requirements are listed below.

  • App icon: a 128x128-pixel app icon in PNG format. The actual icon size should be 96x96 with an additional 16 pixels per side of transparent padding. More details.
  • Promotional image: a 440x280-pixel promotional image. More details.
  • Screenshot: either a 1280x800 or 640x400-pixel screenshot. More details.

Publishing a script to the Chrome Web Store

To register your web app in the Chrome Web Store, follow these steps:

  1. From the Script Editor, choose Publish > Register in Chrome Web Store.
  2. Click the blue "Register Web App" button and wait for a moment while the project is registered. Then, you will see a confirmation dialog, with a link to the Chrome Web Store Developer Dashboard.
  3. Click the link for the Chrome Web Store Developer Dashboard, and from there you will be able to customize your web app listing and publish it in the Chrome Web Store.

Now that your script is registered in draft mode in the Chrome Web Store, you can complete steps 7-9 in the Chrome Web Store's Publishing Your App documentation.

Updating a published script

After you have deployed a web app and published it in the Chrome Web Store, you may find that you want to make changes to either the web app itself, the Chrome Web Store listing, or the app's icon on the New Tab Page.

Updating your web app

If you make changes to your web app, you will need to save and deploy a new version.

  1. Go to File > Manage versions and save a new version of your script.
  2. Go to Publish > Deploy as web app and update the Project version number and then click Update.

Updating your Chrome Web Store listing

If you want to update your Chrome Web Store listing, such as the description of your web app or the screenshots associated with it, visit the Chrome Web Store Developer Dashboard. From there you can edit your item.

Updating your app's icon on the New Tab Page

By default your app will appear with an Apps Script logo on Chrome's New Tab Page after it is installed. To use a custom icon you will need to temporarily host the icon image on a publicly accessible URL and then update the app using the steps below.

  1. Go to Publish > Register in Chrome Web Store.
  2. Click the link titled "specify an alternative image".
  3. Enter the URL of your icon image and click the "OK" button.

This process will copy the image, so further changes to the icon will require repeating these steps.

Removing a script from the Chrome Web Store

To remove a listing from the Chrome Web Store, visit the Chrome Web Store Developer Dashboard. Locate your item's listing and click Unpublish. The listing will no longer be available in the store.

To disable a web app that you've deployed from Google Apps Script, go to Publish > Deploy as web app and click the link to "Disable web app." This will cause your web app to no longer be accessible. You can re-deploy the web app at any time.

Installing a script from the Chrome Web Store

Once you've published a web app in the Chrome Web Store, users will be able to discover it via searching the Chrome Web Store, browsing through categories, or by directly accessing the URL of the listing in the Chrome Web Store. You can learn more about installing free and paid web apps in the Chrome Web Store help center.

Authentication required

You need to be signed in with Google+ to do that.

Signing you in...

Google Developers needs your permission to do that.