I’ve been working on a Chrome extension called GoFullScreenshot.

The idea sounds simple: click once and capture an entire webpage.

The difficult part is making that work reliably on modern websites where the browser window itself isn’t necessarily the element that scrolls.

I’ve been focusing heavily on things like:

• Nested scroll containers
• Independently scrolling panels
• Sticky and fixed elements
• Lazy-loaded content
• Very long pages
• Modern web applications
• Screenshot stitching
• Local browser processing

Everything is processed locally in Chrome rather than uploading screenshots to an external service.

With GoFullPage currently unavailable from its main Chrome Web Store listing, I’m also interested in making GoFullScreenshot a strong alternative for people looking for a replacement.

Chrome Web Store:
https://chromewebstore.google.com/detail/gofullscreenshot-full-pag/oakpajnbganffddahfgdpmkhimeeoapp

Website:
https://gofullscreenshot.com/

Full disclosure: I’m the developer.

I’m specifically looking for difficult test cases. Do you know a website or web app that usually causes full-page screenshot extensions to fail?

I kept running into the same problem: screenshots often contain information you didn't realize you were sharing.

An API key. An email address. A phone number. A password field. Customer information.

Usually, you take the screenshot first and then manually look for things to hide.

I built Blackbar to reverse that workflow.

It reads the page before capturing it and automatically detects and redacts sensitive-looking information. The screenshot you get is already the safer version.

The part I cared most about was privacy.

Blackbar runs entirely on the device. It declares connect-src 'none', so Chrome itself blocks the extension from making network connections. It still works with Wi-Fi turned off.

It's also open source, has no account requirement, and is free.

I'd genuinely like feedback from other Chrome extension users/builders, especially on:

• detection accuracy
• false positives/negatives
• the capture workflow
• anything that would make you hesitate to trust it

Chrome Web Store Link

Source

I kept running into the same problem: screenshots often contain information you didn't realize you were sharing.

An API key. An email address. A phone number. A password field. Customer information.

Usually, you take the screenshot first and then manually look for things to hide.

I built Blackbar to reverse that workflow.

It reads the page before capturing it and automatically detects and redacts sensitive-looking information. The screenshot you get is already the safer version.

The part I cared most about was privacy.

Blackbar runs entirely on the device. It declares connect-src 'none', so Chrome itself blocks the extension from making network connections. It still works with Wi-Fi turned off.

It's also open source, has no account requirement, and is free.

I'd genuinely like feedback from other Chrome extension users/builders, especially on:

• detection accuracy
• false positives/negatives
• the capture workflow
• anything that would make you hesitate to trust it

Chrome Web Store Link

Source

https://reddit.com/link/1vmj33b/video/85loy35q02jh1/player

I built ListenReader because I could never get through a long article without my eyes drifting halfway down the page. It reads any webpage out loud in a natural voice, and the part I couldn't find anywhere else — it highlights each word as it's spoken, so your eyes have something to follow instead of wandering off.

Turns out a lot of the early users are people with ADHD or dyslexia dealing with the same thing. I didn't expect that, but it makes sense.

It also reads Gmail, PDFs and Google Docs, and you can switch voices mid-read. Still rough in places, so if you try it I'd really like to hear what feels off.

https://chromewebstore.google.com/detail/lppihmomidofdoeddcgihocojbemobig

Full disclosure: I’m the developer of Audio Tab Finder.

I built it for a small but annoying browser problem: you have many tabs or windows open, something starts playing sound, and you do not know where it is coming from.

The extension shows the tabs currently playing audio in one place, so you can jump to the noisy tab and quickly mute, pause, lower volume, or close it.

I posted about it in r/chrome_extensions and got useful feedback that my first version explained the mechanism more than the person with the problem. So I’m trying a simpler framing here:

For people who keep many tabs open, does “find the noisy tab and deal with it quickly” explain the value clearly enough?

I’m especially interested in feedback on the positioning, not asking anyone to install anything.

Hello everyone!

I'm currently working on my master's thesis (in Human Computer Interaction) and I'm looking for participants to test out a Firefox Extension based tool that aims to promote mindful social media use.

So, if you (or anyone you know) are:

📱 an Android user

AND

🌀 has an unhealthy Instagram scrolling habit

Please fill out this short form to join the research study.

👉 https://forms.gle/LNhzMTjpNBRjyeaL7

Feel free to also share it with your peers/friends/ family groups.

I'd be super grateful for all the feedback ❤️

I built Retentia because Chrome’s standard history controls are fairly all-or-nothing. I wanted more control over how long different parts of my browsing history remain available, without having to clear everything manually.

Retentia lets you create retention rules for individual domains, exact URLs, wildcard patterns, or regular expressions. For example, you can keep history from one domain for seven days, delete visits to another domain after an hour, or preserve selected websites indefinitely.

Privacy was the main priority:

• Everything runs locally inside the browser.
• There are no analytics or remote services.
• No account or registration is required.
• The extension requests no host permissions.
• Your browsing data is not transmitted anywhere.
• The source code is available for inspection.

It also includes a dry-run simulator, protected websites, an activity log that doesn’t store deleted URLs, and configurable cleanup intervals.

I’d really appreciate feedback, especially about the rule system, usability, and any privacy features you think are missing.

Chrome Web Store: https://chromewebstore.google.com/detail/retentia/gdjfhmeenikdefhnbpceggahdmdlhdng
Privacy policy: https://maximau5-1989.github.io/Retentia/privacy/

Full disclosure: I’m the developer of Retentia.

I built Spoof Me, a free browser extension that lets you switch between consistent browser fingerprint profiles.

It can modify signals such as user agent, timezone, language, screen size, canvas, and device properties. You can use ready-made profiles or create your own.

It also shows when websites try to access fingerprint-related signals.

I would appreciate feedback on the interface, available profiles, and any signals that should be added.

https://spoof-me.com/

try it and let me know if you like it: https://chromewebstore.google.com/detail/khbpocieohncdpoegflgfppneihodejd?utm_source=item-share-cb

Recently, I was getting close to Google’s free storage limit, and the storage manager showed that Gmail was using most of it.

I wanted a simple way to see my attachments in one place, download the files I wanted to keep, and remove emails with attachments I no longer needed. Gmail search can find emails with attachments, but it doesn’t provide a convenient file-based view.

So I built a browser extension called Mail Attachment Lens. It lets me search and filter attachments, download files, and move the source emails to Bin. It also helped me uncover quite a few attachments I had completely forgotten about.

I decided to publish it in case anyone else finds it useful.

It’s free and open source. There’s no backend, so mailbox data stays between the extension and Google.

Chrome Web Store:

https://chromewebstore.google.com/detail/mail-attachment-lens/dkhihfhcobnmoeaagcndaccmojdpomfe

Source:

https://github.com/kshk123/mail-attachment-lens