A Browser AI Tool Field Guide: 40 Projects, 5 Paid Tasks, and the Difference Between Demos and Deliverables
The guide separates tools that merely run in a browser from ones that survive real delivery: edge trimming, field mapping, correction loops, export formats, and re-import. It also demonstrates a disciplined way to test product-market fit without building: check existing paid alternatives, find a repeatable unresolved step, and only then write code.
This is a working reference, not a review roundup. The author screened 40 primary technical candidates and 4 reference or conditional candidates across browser tools for background removal, OCR, transcription, audio enhancement, vectorization, and PDF generation. Each entry lists what runs locally, the model or engine sizes, licenses, and which edge cases remain untested: missed detections, field mapping, export integrity, and human review loops. The recurring conclusion is that a browser demo is not a deliverable; users need the final file, corrected and named, in the right format for their platform.
The second half pivots to five business tasks: supplier CSV to Shopify, client subtitle revisions back into an NLE, booklet imposition, list-driven file renaming, and cross-stitch pattern generation. For each, the author found payment signals in community purchases and reviews, but also existing free or paid alternatives that already cover much of the workflow. The takeaway is not that these markets are dead, but that the missing piece is often a specific handoff step, not another generic tool. The author proposes small, time-boxed experiments to test whether a real pain repeats and whether someone will pay for a standalone fix, before committing to product development. Existing tool features and license obligations are treated as fixed costs, not differentiators.
Most of these tools already do the core computation in the browser; what separates a useful product is the stitching around it: field templates, naming rules, correction UI, export formats, and recovery paths.
The author treats license obligations as a first-class cost, not a footnote: GPL, AGPL, MPL, and mixed model licenses affect whether a tool can be wrapped commercially, and several candidates were excluded or deprioritized purely on license hygiene.
The business task research shows that existing paid alternatives often already cover the full job; the remaining gap is a single handoff step, not a generic feature hole, and targeting that step requires evidence of a repeated failure, not just a forum complaint.
Size of model files is repeatedly decoupled from runtime memory and quality; the author calls out small weights that belie large runtime requirements, and large weights that still produce unreliable output, so resource size alone is a weak proxy for suitability.
The browser is a viable distribution surface for these tools, but after-sales support, payment, refunds, and format upgrades remain real costs that the study does not quantify, and the absence of a reliable cost picture means no profit claim can be made.