So Fakespot shut down some time ago and I kinda missed having something to check amazon reviews with, so I just vibe coded my own version for fun.

when you're on a product it audits all the written reviews and the reviewer accounts, then gives the product a grade and flags anything that looks suspicious. it completely ignores the star-only ratings since there's no real way to check those accounts.

It's not as good as Fakespot, but I think it's helpful in its current state. so I thought I'd share. it's just a personal project and I'm still figuring it out, but I'll keep tweaking it in my free time as people give me feedback. Might just be ai slop but it was fun to create.

anyway, if anyone wants to try it and tell me what's broken, that would help a lot.

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

SnapShotz serves a 2 purposes:
1. Visual context for AI chats
2. For sites AI chats can't read
3. Important Screenshots in the side panel. Through imports.

For me I build my apps and sites in Replit but plan with Claude. So this has been my best way of getting feedback from Claude on visual elements of sites since it wasn't the one to build it. It's also been helpful for sharing context when a chat can't access information through the URL alone.

https://reddit.com/link/1v3xsom/video/h4vxcel6eveh1/player

Hello,

Was looking for some feedback on my chrome extension website?

Stop sharing Chrome Web Store stats as screenshots.

I know how this sounds, but hear me out. This one is a bit different.

KoalaData is mainly for sharing and comparing actual Chrome Web Store stats, which is something I see people asking about here pretty often. Instead of posting 5 different screenshots, you can upload your exported stats (as csv) and share one public page with all the charts.

Once more extensions are added, devs can also compare their numbers and get a better idea of what normal growth, installs or uninstall rates actually look like.

It’s 100% free and open source. No ads, no tracking, no paid tier and no selling your data. I’m not trying to turn it into another analytics subscription.

The site is still in a very early beta, so bugs, missing features and rough edges are expected.

Right now I’m mainly trying to find out whether other extension devs would actually find this useful, so any feedback or problems you run into would help a lot.

Like a lot of people, I had years of saved tabs in Toby when they capped the free plan at 60. That was the push I needed to build the alternative I actually wanted.

TabVault is a tab manager built so it structurally can't do a bait-and-switch:

- Local-first — your collections live in your browser and export to JSON anytime. No account, no server that can hold your tabs hostage.

- Unlimited, free — no caps on tabs or collections, and I've promised publicly that features never move from free to paid.

- One-click import — drop in your Toby export (or OneTab) and everything comes across.

- Optional Pro is $19 once (multiple workspaces, tab-group save/restore, daily auto-backup, Cmd+K palette) — never a subscription.

Built it over a couple of weekends. Sharing it here mostly for feedback from people who live in their tabs — tell me what would make you switch, and what's still missing. Disclosure: I'm the developer.

Chrome Web Store: https://chromewebstore.google.com/detail/tabvault-tab-manager-sess/gfcedicocooccfabphebljcmgpklmimb

Been building Design Snap (pulls design tokens — colors, typography, shadows, radius — from any website, exports to Tailwind v4, shadcn/ui, CSS vars, Figma Tokens) as a side project, runs 100% locally, no account needed. Currently at 1,250+ weekly users, mostly from word of mouth.

Two features keep coming up as "would be nice" and I'm trying to figure out if they're actually worth the build time:

1. Style Dictionary export — instead of just Figma Tokens/JSON/CSS vars, export in the Style Dictionary format so teams with a more formal design system setup can plug it straight into their existing pipeline (iOS, Android, web, etc).

2. Figma plugin — import the extracted tokens directly into a Figma file as styles/variables, instead of manually copy-pasting the JSON export. Probably starting as a simple "import this file" plugin rather than a live sync, to keep things local/no-backend like the rest of the extension.

For anyone working with design systems or Figma tokens day to day — would either of these actually save you time, or is this solving a problem that doesn't really exist ? Curious which one you'd want first if you had to pick.

Small utility extension, ~500 installs over about 3.5 months. Pulled the 180-day CSV export and the OS split is strange enough that I want a sanity check from people who have seen more data than me.

Installs / uninstalls / rate:

• Windows: 257 / 129 = 50%
• ChromeOS: 155 / 3 = 2%
• Mac OS: 66 / 37 = 56%
• Linux: 7 / 8

ChromeOS is 30% of all installs and essentially never churns, while both real desktop platforms lose about half. I have no ChromeOS-specific feature and I have done zero marketing anywhere near education or enterprise.

My assumption is admin force-install (Google's docs say force-installed items can't be removed or disabled by the user), which would explain the 2% mechanically. Three things I can't work out:

1. Is there any way to see from the developer dashboard whether installs came from an admin policy rather than users choosing to install? I don't see a breakdown for it
2. Is a near-zero uninstall rate on ChromeOS a reliable tell for force-install, or do ChromeOS users just genuinely behave differently?
3. This is the one that actually affects my numbers: do force-installed users count towards "weekly users" even if they never open the extension? If they do, my engagement numbers are inflated by a cohort that never chose the thing, and my real churn among people who opted in is ~53% rather than the 35% the dashboard reports.

Mostly trying to figure out whether to treat the ChromeOS block as a distribution channel worth understanding, or as noise I should exclude before reading any retention number.

Hey everyone, I’ve been working on a Chrome/Edge extension called copy++ Browser.

It lets you save text, image URLs, references, and snippets into a local browser stack instead of losing each item when you copy something new.

I just added a few new features:

• Export the whole saved stack to XML
• Import XML back into the extension
• Drag items into whatever order you want
• Keep the context-menu paste/delete order matching the popup order
• Export a single saved item as PNG or PDF
• Use the exported item files with LLMs, docs, or other workflows

The XML export/import is meant for backup and moving saved stacks around. The drag ordering is useful when you’re building a prompt, collecting research, or arranging snippets before pasting/exporting.

I'm a Uni Student and I use Claude for hours every day and the blank interface was starting to feel really sterile. I wanted something that felt a bit more alive without being distracting.

So I ended up building a Chrome extension that adds animated backgrounds and themes, which was inspired by wall paper engine on Steam. Not just recolouring, actual subtle animation, that kind of thing. They move quietly in the background while you work.

It's called Vellum and its roughly got around 100 themes organised into categories (space, nature, weather, retro, minimal, etc). A chunk of them are free forever, no account needed, and it works on Claude and others!

I just wanted to share it here and show you guys, please give me your feedback and any themes you want to see, I'm happy to add them in the next update!

https://chromewebstore.google.com/detail/vellum-animated-themes-ba/pnpplaegcahgbndhahihciknencicpjn?authuser=0&hl=en

I take a lot of notes from YouTube/Bilibili videos and I was tired of two things: AI "summaries" that flatten everything into the same three bullets, and tools that paste in random frames that don't actually match what's being said.

So I built Video Learning Wiki — a browser extension + a local backend. You watch a video normally; when you're done you click one button and it produces a structured, illustrated study report, then files it into a growing local wiki. The idea (borrowed from Karpathy's "LLM Wiki") is that each video adds a page, so it compounds over time into your own knowledge base instead of a pile of one-off summaries.

The part I'm actually proud of is that it tries hard not to make things up:

\- A visual evidence gate. Before any screenshot goes into your notes, a separate vision model checks it against the transcript. If the frame doesn't support what's being said, it gets dropped, and the writer is blocked from referencing it. You get pictures only where the picture earns its place.
\- Screenshot density adapts to the video. A step-by-step tutorial gets captured densely; a talking-head explainer barely gets any frames, because the subtitles already say it.
\- Plain deterministic code sits between the model calls — topic weighting, screenshot budget, anchor picking. Models only judge and write; the logic in between is testable and reproducible.

Everything runs locally (FastAPI backend + your own model API key). Output is a self-contained HTML file plus markdown for Obsidian etc.

Repo + a real example report (generated from an Anthropic "Code w/ Claude" talk):
https://github.com/ggl003614-tech/video-learning-extension

Honest status: it's v0.1 and dev-stage — you load the extension unpacked and run the backend yourself. And the big one: reports are generated in Chinese right now (that's my language); configurable output language is the very next thing I'm building. So today you'll get more out of the architecture than the notes themselves, unless you read Chinese.

Happy to answer anything about the pipeline — the evidence-gate + adaptive-capture design was the fun part to get right.

So apparently I'm not the CEO of a startup. I'm the CEO of Delusion. 💀

Built a Chrome extension to track time per site and expose my own lies. Numbers don't care about your self-image.

• Tracks time on every website
• Everything stays local, no accounts, no servers
• Open source

If it judges you as hard as it judged me, it's working.

Repo: https://github.com/HariNayan/Screen-Time-Tracker-Chrome-Extension

I often find an image on Google Images, open the original article, and then have to scroll through a huge gallery to find the same image again.

So I built Pinpoint, a Chrome extension that adds “Find This Image on Source Page” to the right-click menu.

It opens the original page, locates the matching image, and scrolls directly to it.

I’m currently testing it across different websites and image layouts.

Honest question: would you use this often enough to keep it installed?

Chrome Web Store: Pinpoint

Like many of you I kept hitting the 5-hour limit with zero warning, so I built a small Chrome extension that pins Claude's own usage numbers to the page:

5-hour limit as a bar with a "resets in …" countdown (turns red at 100%)

- Hover for weekly, extra credits and Routines

- A donut showing how much of the 500k/1m context window the current chat uses

- An hourglass counting down the prompt cache, so you know when a quick follow-up is still cheap

It's free and open source (MIT), uses the same internal endpoint as Settings → Usage, and has no analytics or external servers: the only permission is storage. 14 languages.

> Chrome Web Store: https://chromewebstore.google.com/detail/usage-bar-for-claude/imblbfhdbdecholhjbagcjahdkhidneb

> Source: https://github.com/disi910/claude-usage-bar

Feedback very welcome, especially from Team-plan folks, since I can only test the rows my own plan returns. If it's useful, a review on the Web Store genuinely helps a solo project.

I use Claude every day and kept running into the same wall: there are no folders, search is weak, and there's no real way to get a conversation out. After a few hundred chats I had no idea where anything was.

So I built a small extension to fix exactly that. It adds a sidebar to claude.ai with:

- Folders: Colour-coded, drag-and-drop, or right-click to file a chat

- Search: Find any conversation by title

- Export: Save a full conversation to Markdown or PDF (the whole thing, in order,

not just what's on screen)

A few things I care about and figured this crowd would too:

- Your folders are stored locally in your browser. No account, no server, no tracking.

- Export pulls your own conversations from your own logged-in session, nothing is

sent to me.

- It's an independent project, not affiliated with Anthropic.

It's free to use (up to 3 folders, title search, Markdown export of the open chat).

There's an optional paid tier for unlimited folders, PDF, and bulk-exporting a whole

folder at once. Just being upfront so there's no surprise paywall.

It's brand new, so I'd genuinely love feedback: what's missing, what's annoying,

what would make it actually useful for how you use Claude. Full-text search and

nested folders are already on my list.

Link in the comments. Happy to answer anything.

I built a Chrome extension that shows Claude usage limits in the sidebar because I was checking the settings page constantly.

The useful part is completely free. The only paid features are themes, colors, and indicator styles through a one-time lifetime upgrade — no subscription.

My thinking was that nobody wants another monthly charge for a small utility. But now I’m wondering if cosmetic features convert at all, and whether lifetime pricing is a mistake.

Has anyone tried this model for an extension or small tool? How did it perform?

Hello, chrome extensions users and redditors, Im here to ask if theres any extension or way to lock a profile behind a password. I share a computer, and its tedious to log in and log out of websites just for the sake of my privacy.

Is there any way I can configure a password in order to access my profile, or something similar through an extension? Please let me know

(sorry if the post is low quality i rarely use reddit and less post)

Two things pushed me into building this. First was just normal dev work: I'd be in the middle of something and need to hand a piece of the page to an AI tool, and the only way to get it was popping open devtools, inspecting the element, right-clicking, copy, outerHTML, paste. Every single time. I wanted to just hover over the thing and grab it, or grab a whole page at once and have it sitting in a folder ready for whenever I actually needed it, instead of going back into the debugger and re-collecting it on demand.

Second thing was targeted captures specifically. I'd been using a screenshot-and-hand-to-AI workflow for that, which is fast but the model misreads text often enough that I stopped trusting it for anything that mattered. Copy-pasting the real text is accurate but it's slow and it's annoying to do it ten times in a session. I wanted highlight, click, done, with the actual text and not a guess at it.

So I built Aura Extract. Hover over any element and it captures just that node's clean HTML with no side effects on the page itself, nothing added, nothing left behind once you're done.

Every capture does both automatically, copies to your clipboard and writes a file, so it's there either way you want it. In practice, if it's something small I'm almost always just pasting straight from the clipboard into a chat. If it's something big, like a whole page, I'll point the AI at the file itself instead of pasting it in, mostly because dumping a massive block of text into a chat window risks blowing right past the context limit before the model even gets to the part I actually care about.

Markdown is the default since that covers most of what I actually need, but you can grab stripped-down HTML or the full raw HTML too, if you're after the actual page structure for something like figuring out how a layout's built rather than just reading the content. Markdown's the default because raw HTML through a naive converter drags along scripts, styles, and layout cruft that eats tokens for nothing, so Extract runs everything through three stages before it writes anything: strip the junk, run Mozilla's Readability to isolate the actual article content, then convert what's left to Markdown. Typically cuts 20 to 40 percent off the token count versus dumping raw HTML, and what's left is something simple enough a model can actually use instead of picking through div soup.

There's also a crawl mode for full docs sites, click a sidebar or table of contents and it follows every link, fetches each page, and writes the whole thing to a local folder with an index that has all the internal links rewritten to point at your local copies. Handy for dropping a whole SDK's docs into Cursor or an AI IDE in one shot instead of forty separate copy-pastes.

Happy to answer questions in the comments.

Wanted to share a small win but it's been so much fun 😭.

This is genuinely the first app I've ever shipped. I built it mostly to learn how to actually take something from idea to getting my first (free) users Wasn't expecting much.

For context, I built a Chrome extension that reads text aloud: highlight anything on a page, right-click, and it reads it back to you. Essentially a text-to-speech reader with an interactive panel that lets you skip parts.

I underestimated how much work goes into something like this. A few things that ate way more time than I planned for:

• The panel/settings UI alone went through probably 6-7 rewrites, trying to fit a voice picker, speed control, and language handling into something that doesn't feel cluttered is harder than it looks.
• So many APIs!
• Bugs I didn't see coming: text getting cut off mid-sentence on certain sites, the right-click menu occasionally not registering on dynamically loaded content, and one memory leak that only showed up after leaving a tab open for hours.
• I had to make sure the panel had a nice interface and felt better than my competition and AI chatbot voice readers!
• The text panel lets you jump to the text you want to read any any chatbot :D.

Genuinely didn't expect the "boring" plumbing to take more time than the actual feature. But 192 installs in and still can't believe strangers are using something I built.

Next up is figuring out growth. Ran an SEO agency for years in a past life before I burned out of that world, so I'm planning to lean on that background instead of paid channels, curious how that translates to growing a Chrome extension versus a website.

Open to feedback on any of the above, or thoughts from anyone who's hit similar walls building their first extension.

192 installs and 3 weeks in, still can't quite believe strangers are actually using something I built. Genuinely excited to see where this goes.

Now that the core is solid, next step is figuring out growth, which is actually the part I'm most comfortable with. I ran an SEO agency for years in a past life before I burned out of that world, so I'm planning to lean on that background for organic growth rather than paid channels. Should be a fun test of whether SEO instincts translate to growing a Chrome extension.

Open to any feedback on the extension itself, or thoughts from anyone who's grown an app without ads.

Hey everyone,

Like many of you, I spend a huge amount of time watching technical tutorials, bootcamps, and coding lectures on YouTube.

Over time, I noticed a frustrating pattern in my own learning workflow:

• Tab-switching fatigue: Constantly pausing videos and switching back and forth to type notes.
• Manual visual capture: Taking screenshots manually, cropping them, and trying to align them with video timestamps.
• Context switching: Getting pulled into background tab distractions and losing focus mid-lecture.

When looking at existing video note-taking tools, many forced all study notes onto central servers, locked basic utility behind monthly subscriptions, or required mandatory cloud accounts. I wanted a clean, distraction-free study environment that respects user privacy and runs entirely offline. So I built VCrumb AI.

🛠️ Key Architectural Decisions & Technical Highlights

Since this was built for developers and heavy learners, here were the core design choices:

• Local-First Architecture (IndexedDB): All rich-text notes, timestamp links, and screen captures live strictly inside your browser's local storage. Zero cloud lock-in, zero server dependence, and 100% offline access as a core experience. (Cloud sync options will be purely optional in future releases.)
• Side-by-Side Canvas: Instead of an overlay blocking video controls, the interface embeds directly side-by-side with the YouTube player for seamless rich-text editing and instant, timestamped screenshot captures.
• Bring Your Own Key (BYOK) AI Integration: Instead of forcing a $15/month subscription for video summaries or Q&A, users can optionally plug in your own OpenAI or Gemini API key. If you don't want AI, the core note-taking utility remains completely free and local forever.

Request for Feedback

We just made the official community release on Product Hunt !

As a solo developer, I’d love honest feedback from this community:

1. How is the side-by-side layout experience on smaller screens or laptops?
2. What features or export formats (e.g., Markdown, PDF) would make this most useful for your study workflow?

(Links to the Product Hunt launch page and Chrome Web Store are posted in the first comment below!)

Would love to hear your thoughts, feature requests, or critiques in the comments!

I use Gmail heavily, but my inbox is constantly filled with newsletters and subscription emails. I got tired of opening Gmail.com just to read, archive, unsubscribe, create a label, or send a quick reply.

So I built a Chrome extension that lets me handle these tasks directly from a small popup. It isn’t trying to replace Gmail—just make everyday inbox cleanup faster.

I originally built it for myself, then thought about publishing it. After finishing nearly everything, I discovered that the Gmail permissions it uses require an annual third-party security assessment costing around $675.

Classic indie-developer timing: discover the recurring compliance bill after building the product.

Now I’m wondering whether anyone else would genuinely use—and pay for—something like this. If I can find around 100 people who would, I’ll bite the bullet and pay for the assessment 😄😄.

Would this be useful to you? If you’re curious, leave a comment and I’ll share more.

Hey all, I created this extension to solve my own issue of having to wait for an AI (Chatgpt and Gemini in particular) to finish replying in order to send the next prompt.

Essentially, it queues each of your prompts and sends them automatically one after another after the AI has finished responding for

Feel free to take a look: https://chromewebstore.google.com/detail/ai-prompt-queue/ddpfghjgnlkhkgeaaknhkaglichonopa?authuser=0&hl=en

I’ve been using Cloudflare across many of my projects for more than 12 years. Whenever I visit a website, I’m often curious whether it also uses Cloudflare products, e.g., dns proxy, cdn, waf, and more.

So I asked Codex to build a simple Chrome extension to look for several Cloudflare-related signals, including response headers, cookie names, and JavaScript global variables. Detection happens entirely through local JavaScript in your browser.

No browsing data is sent over the network. Everything stays on your device.

Chrome Web Store:

[https://chromewebstore.google.com/detail/techflare/lbbkmioghlgfnbkciibfglcopkncdfpg\](https://chromewebstore.google.com/detail/techflare/lbbkmioghlgfnbkciibfglcopkncdfpg)

Please help, any way around. Confirmed from my bank they are saying no issue from their side.