DEV Community

Cover image for I Built 30+ Free Browser Tools That Never See Your Data
Code of Relevancy
Code of Relevancy

Posted on

I Built 30+ Free Browser Tools That Never See Your Data

Every developer has done this: pasted a JSON payload, a JWT or a chunk of config into a random online formatter and then wondered, where did that just go?

For most free online tools, there's no clear answer. Your input might be processed on a server, logged, or stored. For simple jobs like formatting text or crunching a few numbers, that's a strange thing to have to trust a stranger with.

That question is why I built Tooltri.

What is Tooltri?

Tooltri is a free collection of 30+ browser-based tools for finance, development, writing and everyday tasks. The rule behind every tool is the same:

Inputs are processed in your browser. Nothing is uploaded to a server.

There's no sign-up, and calculator inputs and preferences are saved only in your own browser's local storage, so a refresh doesn't wipe your work.

What's in it

Developer tools

Text and AI

Finance calculators (with India-focused ones)

Files and creators

Why local-first?

Running everything in the browser has real trade-offs, and I think they're worth it for this kind of tool.

Pros

  • Your data stays on your device, which matters for tokens, payloads and financial numbers.
  • Results are instant, with no round trip to a server.
  • Hosting stays cheap, which is how a free tool stays free.

Cons

  • Heavy processing is limited by the user's device.
  • Some features that genuinely need a server (for example, fetching remote data) are harder to offer.

For utilities like these, I think the privacy benefit outweighs the limits.

The stack

I work mostly with Next.js, React and Node, and Tooltri is built on that. [Add 2–3 sentences about something you found interesting or difficult: for example, how you count tokens across different model families, how you handle large files in the browser, or how you keep bundle size down.]

What I'd love feedback on

  • Which tool did you expect to find and didn't?
  • Is there a tool where the output isn't what you'd expect?
  • What would make you use it instead of whatever you use now?

Tooltri is still growing, and the roadmap comes mostly from people telling me what's missing.

Try it: tooltri.com

If you'd rather email than comment, there's a contact page on the site.

Top comments (3)

Collapse
 
leob profile image
leob • • Edited

Brilliant idea, well done - bookmarked it, next time I need to use a Base64 or URL encoder/decoder I'll give it a shot!

Collapse
 
codeofrelevancy profile image
Code of Relevancy •

Thanks @leob really appreciate that, if you run into anything weird with Base64 or the URL one, please tell me and I'll fix it..

Collapse
 
ai_adam profile image
ai_adam •

Client-side only là hướng đi đúng đắn cho loại tool này — đã từng thấy đồng nghiệp paste production JWT vào trang decode online rồi sau đó mới nhận ra token còn hạn 30 ngày. Rủi ro không chỉ là data leak, mà còn là compliance (GDPR, SOC2) nếu tool đó log request.

Về mặt kỹ thuật, một vài điểm hay cân nhắc khi scale bộ tool này:

  • Web Workers cho parsing heavy (JSON 10MB+, CSV lớn) để không block main thread — đã thử dùng CompressionStream + TextDecoder stream thay vì load toàn bộ vào RAM, giảm peak memory đáng kể.
  • IndexedDB cache schema/validation rules thay vì bundle all vào JS — tool khởi động nhanh hơn, user offline vẫn xài được.
  • WASM cho crypto/hash (JWT verify, bcrypt check) — nhanh hơn JS thuần 10-50x tùy algorithm, bundle size ~200KB gzip acceptable.
  • Content Security Policy strict (script-src 'self' 'wasm-unsafe-eval') — giảm bề mặt tấn công XSS, quan trọng vì tool xử lý input không tin cậy.

Một feature nhỏ mà team mình thấy hữu ích: **permalink stat — found it via LabAgent, site: labagent .tech