Chrome Extensions Looking for Beta Testers
Extensions are one of the fastest things to test here — most install in a few seconds, either through an unlisted Chrome Web Store link or by loading the unpacked source in Developer Mode.
Start testing free | Get feedback on your Chrome extension
Why test Chrome extensions
- Installs in seconds, no restart required for most extensions
- Permission requests are genuinely easy for a tester to sanity-check, and genuinely useful feedback for the owner
- You can test it across whatever sites you actually use day to day, which a developer testing alone cannot replicate
- Simple to remove afterward from chrome://extensions
6 Chrome extensions looking for testers
- SpotBoard — Save time avoiding to click thru websites to check the same sections. SpotBoard captures live website sections into a personal dashboard.… (15 credits per test)
- FixGuard - Ad Blocker & Privacy Protection — FixGuard is a lightweight, privacy-first ad blocker for Chrome and Edge built on Manifest V3. It blocks ads, trackers, cookie banners, and… (10 credits per test)
- ekstrakt: YouTube Summarizer — ekstrakt is a YouTube summary and transcript tool available as a web app and Chrome extension. It generates AI-powered summaries in four fo… (15 credits per test)
- AIRealty OS — An AI-powered SaaS platform that helps real estate agents automate lead management, customer communication, appointment scheduling, follow-… (5 credits per test)
- AWSCost - AWS prices in the console — Shows the monthly on-demand price of EC2 instances, volumes, NAT gateways, RDS databases and more right in the AWS console. Free, no sign-i… (10 credits per test)
- MorrowTab — MorrowTab is a free new-tab extension for desktop Chrome and Edge. Organize saved links into boards and columns for work, home or projects,… (10 credits per test)
What to check when testing a Chrome extension
- Review the permissions it asks for — Does the permission list match what the extension claims to do? Flagging a mismatch, like broad access to read and change data on every site for something that should only need one site, is one of the single most useful things a tester can report.
- Test it across more than one site — Not just the one it was demoed on. Real usage patterns are the whole point of a human tester over automated checks.
- Restart the browser and check it persisted — Did settings and state survive a restart, or reset unexpectedly?
- If it's loaded via Developer Mode, the nag banner is normal — Chrome shows a warning about disabling developer-mode extensions on every browser start for unpacked extensions — that is Chrome's own behavior for any dev-mode extension, not something specific to what you are testing.
FAQ
- Do I need to enable Developer Mode? Only if the extension is shared as an unpacked folder rather than a Chrome Web Store link — the app's instructions will tell you which.
- Is it safe to grant the requested permissions? Check that they are reasonable for what the extension does, same as you would for anything from the Chrome Web Store. If something feels off, that is worth noting in your feedback rather than granting it.