Charles
  • Introduction
    • 👋Welcome
  • Getting started
    • Quickstart guide
  • Opening actions
    • Popup, side bar and modal options
    • Trigger the extension with a floating button
    • Open the extension automatically on specific URLs
  • Key features
    • Features overview
    • Open website on install / uninstall
    • Get tab info
    • Get text selected by user
    • Get element text
    • Get element HTML
    • Set element inner text
    • Set element inner HTML
    • Open URL in sidebar modal
    • Open URL in fullscreen modal
    • Copy text to clipboard
    • Populate an input field
    • Simulate mouse click on an element
    • Capture screenshot
    • Open URL in new tab
    • Show native alert
    • Set an extension badge color and text
    • Change extension icon
    • Close extension
    • Save to Chrome storage
    • Injecting custom javascript
  • Extending Charles
    • Extending Charles with your own Javascript
  • Publishing to the Chrome Webstore
    • Prepare extension for submission
    • Registering as a Chrome Webstore developer
    • Publishing your extension
  • FAQ
    • Common questions
  • Troubleshooting
    • Charles Data Elements do not receive any values
    • Cannot log in (cookie issues)
    • Support
Powered by GitBook
On this page
  1. Publishing to the Chrome Webstore

Prepare extension for submission

PreviousExtending Charles with your own JavascriptNextRegistering as a Chrome Webstore developer

Last updated 5 months ago

To publish your extension to the Chrome Webstore follow the steps in the . But let’s tidy your extension up before doing so:

  1. Open manifest.json in any text editor and adjust the app name and description in line 3 and 4

  2. Make sure to delete the content script section from manifest.json if you don’t use any content scripts in your extension. Otherwise your extension might be rejected by Google.

  3. Delete unused permissions from the manifest.json file. EG if you don’t use the Chrome local storage workflows in your extension, delete the line "storage", in manifest.json. You will most likely always need activeTab and scripting. Once you delete any permissions, please test if you app still works correctly.

  4. If you have a square icon for your Chrome extension, use an online resizing service (e.g. ) and replace the files in the images folder. Make sure to keep the names as is (i.e. 16x16.png, etc.).

  5. If you don’t need microphone access from your sidebar, please comment out (i.e. add // in front of the line) lines 168, 253 and 301 in background.js

Chrome Developer Docs
https://www.simpleimageresizer.com/upload