manifest.json directly to unlock browser features that require explicit configuration — like keyboard shortcuts, web-accessible resources, or custom icon sets.
Edit the name, version, and description
Openmanifest.json and update the top-level identity fields:
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:
Some APIs (like
"tabs" and "history") require user consent and display a warning during installation. Only include permissions your extension actually needs.Adjust content script match patterns
Control which pages your content scripts run on by editing the"matches" array under "content_scripts":
- Specific domain
- All HTTPS pages
- Multiple domains
example.com.Update icon paths
Replace the generated icon placeholders with your own files. Icons must be PNG files at each declared size:chrome://extensions.
Add keyboard shortcuts
Use the"commands" key to register keyboard shortcuts:
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":