How to Suggest Features to Chrome Extension Developers

Most Chrome extensions are made by small teams or a single developer, and many features exist because a user asked. A clear request sent to the right place has a real chance of being built.

Where to send it

1. The Support tab on the extension's Chrome Web Store page, if the developer has turned it on.
2. The developer's website or email, listed on the store page under the extension's details.
3. GitHub issues for open-source extensions. Search existing issues first, and add a thumbs-up to a matching request rather than opening a new one.
4. The extension's own feedback link, often in its pop-up or options page.

Why reviews are the wrong place

A one-star review saying "needs dark mode" is easy to miss, hard to reply to in detail, and hurts a small developer's ranking. Use reviews for your overall opinion, and send requests directly.

How to write a request that gets read

• Describe the problem, not just the solution: "I can't tell which sites I've excluded" gives the developer room to find the best fix.
• Explain your use: what you were trying to do, and how often.
• Be specific: which site, which setting, what you expected to happen.
• Add a screenshot or a short screen recording.
• Include versions: the extension's version from its details page at chrome://extensions, and your Chrome version from chrome://version.
• One idea per message, so each can be tracked separately.

Bug or feature?

If something that used to work has stopped, it's a bug. Say so clearly, list the steps to reproduce it, and mention any recent Chrome update. Bugs usually get fixed faster than new features.

Set realistic expectations

• Developers weigh requests against how many people want them and how hard they are.
• Some requests can't be done because of Chrome's rules, such as the limits Manifest V3 places on extensions.
• A polite follow-up after a few weeks is fine; repeated demands aren't.

Help in other ways

• Leave a fair review once a request is handled.
• Share the extension with people who'd find it useful.
• For open-source projects, contribute code or translations.

Have a request for a Bushe.co extension? Use the contact page. If you need a custom extension built for your business, see Chrome extension development.