I built a free Chrome extension that turns screenshots into PDF reports
I kept watching developers and QA engineers do the same painful thing.
Take 6 screenshots during testing. Open Google Docs an hour later. Spend 30 minutes reconstructing context they no longer remember. Annotate in a separate tool. Copy paste. Reformat. Export.
Every single report. Every single time.
The tools existed in pieces, screenshot tools, annotation tools, document editors, PDF exporters. Nobody had connected them into one workflow for the specific job of visual documentation.
So I built SnapDoc.
Capture → Annotate → Add context → Export PDF. One tool. Under 2 minutes.
Honest numbers so far:
100+ installs on Chrome Web Store
13 weekly active users (retention is the real problem)
Zero marketing budget
Completely free, no account required
Would love brutal feedback from this community, especially on the retention problem and the free vs paid decision.
Landing page: getsnapdoc.com
Chome Store: https://chromewebstore.google.com/detail/kbekamnlgnmmoaijfggiahmpadpkadeh?utm_source=item-share-cb
What would make you actually come back to a tool like this after installing it?
how do find users for a extension like this? i dont think SEO would work for it. do u run ads?
This is a clever niche.
I’ve seen a lot of teams doing exactly this manually — screenshots from dashboards → pasted into docs → turned into reports.
The interesting question is always where the real value sits:
is it the conversion step, or the organization and annotation of screenshots afterward?
How are people mainly using it so far — reporting, documentation, or sharing insights?
mainly this is about reporting, I am gonna add more reports categories in next phase.
That makes sense — reporting tools usually evolve that way.
From what I've seen, categories start to matter once people reuse reports across different contexts (bugs, QA notes, product feedback, etc.).
Are you thinking of categories mainly as organization for the user, or as a way to generate different report formats later?
focusing on bunch of reports formats ( documents, feedbacks, notes, bugs )
to increase target audience
That makes sense — different report formats can definitely widen the use cases.
The tricky part I’ve seen is keeping a clear “primary workflow” so the product doesn’t feel like a toolbox.
Which format is actually the main use case right now — bug reports, documentation, or feedback capture?
Its bug report mainly focused right now
Bug reporting is a strong use case.
A lot of teams still rely on scattered screenshots in Slack or long text descriptions, which makes reproducing issues harder than it should be.
If the workflow makes it easier to capture context and turn it into a structured report, that’s already a big improvement.
Are you focusing more on developers, QA teams, or non-technical users reporting issues?