Skip to main content

Store Submission

Submitting to the Chrome Web Store, Firefox Add-ons, Microsoft Edge Add-ons, or Safari Extensions is straightforward, but missing a step can delay approval by 3–5 business days. Use this checklist before you hit Submit.

Chrome Web Store​

Developer Account​

  • Developer account at chrome.google.com/webstore/devconsole — one-time $5 fee
  • Payment profile linked if you charge for the extension (required even with Stripe)
  • 2FA enabled on your Google account

Extension Package​

  • Production build: pnpm build:chrome
  • Loads cleanly on a fresh Chrome profile with no console errors
  • All features tested — auth, billing, core functionality
  • Version in manifest — start at 1.0.0, not 0.x.x
  • Description filled (max 132 characters for short description)
  • Icons included: 16×16, 48×48, 128×128 PNG
  • Permissions audited — privileged permissions must be optional (see Manifest Permissions)

Store Listing Assets​

  • Store icon: 128×128 PNG
  • Promo tile: 440×280 PNG (for category pages)
  • Screenshots: 1–5 images, 1280×800 or 640×400, showing real UI
  • Promotional video (optional): YouTube URL, 30–90 seconds

Store Copy​

  • Name: Clear, no competitor brands, under 75 characters
  • Short description: 132 characters, benefit-focused
  • Detailed description: What it does, why install, how to start
  • Category selected (Productivity, Developer Tools, etc.)

Privacy & Legal​

  • Privacy policy URL — required if you access any user data (including storage)
  • Privacy policy hosted at a stable URL (not localhost or gist)
  • Data disclosure completed in the developer console
  • Permission justification written for each sensitive permission

Submission​

  • Developer notes filled in — explain account/setup if reviewers need to test
  • Confirmation email received — review usually takes 1–3 business days

After Approval​

  • Store URL saved and shared
  • Update pipeline tested — submit a minor version bump to verify the process
  • Support channel ready — email or help page for users

Common Delays (Not Rejections)​

  • Missing privacy policy for an extension that uses storage
  • Incomplete data disclosure form
  • Screenshots that don't match described functionality
  • Developer notes absent when account/setup is required to test

Address these before submission to avoid 3–5 day follow-up cycles.

Firefox Add-ons​

  • Build with pnpm build:firefox
  • Submit at addons.mozilla.org/developers
  • Firefox requires browser_specific_settings.gecko.id in the manifest (already configured in LightningAddon)
  • Review process is similar; Mozilla documentation has the full checklist

Microsoft Edge Add-ons​

Safari​

  • Build with pnpm build:safari (macOS only)
  • Requires Apple Developer account for App Store Connect
  • See the Safari guide for packaging, local testing, and store submission