Skip to main content
After downloading your extension from Extensy, you can open and edit manifest.json directly to unlock browser features that require explicit configuration — like keyboard shortcuts, web-accessible resources, or custom icon sets.
Manual edits to manifest.json are local only. They will not sync back to Extensy. Keep a backup of your edited file before re-generating the extension.

Edit the name, version, and description

Open manifest.json and update the top-level identity fields:
Increment version each time you publish an update to the Chrome Web Store.

Add or remove permissions

Add permissions to the "permissions" array to request access to browser APIs. Remove any permissions your extension does not use — the Chrome Web Store flags unnecessary permissions during review. Before:
After (adding tabs and alarms):
Some APIs (like "tabs" and "history") require user consent and display a warning during installation. Only include permissions your extension actually needs.
Common permissions and when to use them:

Adjust content script match patterns

Control which pages your content scripts run on by editing the "matches" array under "content_scripts":
Runs only on example.com.

Update icon paths

Replace the generated icon placeholders with your own files. Icons must be PNG files at each declared size:
Place your icon files in the same directory structure you reference above, then reload the extension in chrome://extensions.

Add keyboard shortcuts

Use the "commands" key to register keyboard shortcuts:
Listen for the command in your background service worker with chrome.commands.onCommand.addListener.

Make assets accessible to web pages

If a content script needs to load images or scripts from your extension package into the page, declare them under "web_accessible_resources":
After declaring a resource, reference it in your content script using: