Skip to main content
A functional extension is only half the work. Your store listing needs high-quality visual and written assets to attract users and pass Google’s review. Gather everything below before opening the Developer Console.

​
Asset checklist

  • Extension ZIP — your Extensy-generated package, tested and ready to upload
  • Store icon — 128×128 px PNG, shown to users browsing the store
  • Screenshots — at least 1, up to 5; dimensions must be 1280×800 px or 640×400 px
  • Short description — max 132 characters; appears in search results
  • Detailed description — explains what your extension does, who it’s for, and how to use it
  • Category — the most relevant category (e.g., Productivity, Developer Tools, Shopping)
  • Privacy policy — required if your extension collects any user data

​
What Extensy provides vs. what you supply

Use the 128 px icon from your extension’s icons/ folder as a starting point for your store icon. Tools like Figma or Canva make it easy to refine it for a professional finish.

​
Designing your icon

Your icon is the first thing users see in search results. It should be clear, recognizable, and consistent with your extension’s purpose. The store requires a 128×128 px PNG — the same size Extensy includes in your ZIP.
Chrome also uses 16 px and 48 px icons internally (toolbar, extensions page). Extensy generates all three sizes. You only need to supply the polished 128×128 version for the store listing.

​
Capturing effective screenshots

Screenshots show users what your extension looks like in action before they install it. Aim for clarity over decoration.
  1. Popup view — show the extension’s popup UI with real content visible.
  2. On-page injection — if your extension modifies a webpage, show a before-and-after comparison.
  3. Action shots — capture a user interacting with a button, badge, or highlighted element.

​
Writing your store listing

Your descriptions must be clear and professional. Avoid vague claims — focus on what the extension actually does.
“Track prices effortlessly. Highlights local currency symbols and calculates the total sum on any e-commerce page automatically.”
What it does: A clear 1–2 sentence overview.Key features:
  • Feature one
  • Feature two
  • Feature three
How to use:
  1. Go to any supported site.
  2. Click the extension icon.
  3. See the result inline.
Privacy: State what data you access (if any) and why.
“This extension does not collect or store any personal data. All processing is done locally on your machine. We do not use remote servers or trackers.”
If your extension accesses browsing history, login tokens, or any personal data, you must provide a link to a hosted privacy policy page. A Google Doc or a simple static page both work.

​
Justifying your permissions

For every permission declared in manifest.json — such as storage, tabs, or activeTab — you must write a one-sentence justification in the Developer Console.
Example: “Storage permission is used to save your preferred theme color across browser sessions.”
Be specific. Vague justifications like “needed for functionality” are a common reason for rejection.
Do not use trademarked brand names in your extension’s name unless you own the trademark. Instead of “Facebook Enhancer”, use “Enhancer for Facebook”.