How Tabreon Works
A plain explanation of what actually happens when you use a Tabreon tool.
Quick answer
Most Tabreon tools — text, developer, QR, image, and PDF tools — run entirely in your browser using JavaScript. Your files and text are processed on your own device and never uploaded to a server. A few community features (feedback, early access, feature requests) send data to Tabreon's servers to work, and say so explicitly.
Step by step
- 1Open the tool. Navigate to any Tabreon tool page. There is no sign-up, no install, and no waiting for a server to spin up.
- 2Add your input. Paste text, or select a file with your browser's native file picker. It's read into your browser's memory on your own device — it is not uploaded anywhere.
- 3Processing runs locally. JavaScript running directly in your browser tab transforms the input — formatting JSON, resizing an image, merging a PDF — entirely on your device.
- 4Get your result. The output renders immediately in the page, and downloads are written straight from your browser to your disk. Nothing round-trips through a Tabreon server.
What runs locally vs. what needs a server
Runs entirely in your browser
- Text tools
- Developer tools
- QR code generator
- Image tools
- PDF tools
Your input never leaves your device. Closing the tab discards it — there is no server-side copy to delete.
Uses a server, and says so
- Feedback form
- Early-access signup
- Feature-request board (including voting)
These community features need a server to store what you submit. Each one is labeled, and only stores what you explicitly give it — for example, an email address for early access, or your feedback text.
Common misconceptions
- "Free web tool" does not automatically mean your files are uploaded — check whether the tool actually needs a server round trip for what it does.
- A tool can be free and still process data server-side; Tabreon's core tools are free specifically because they run on your own device, not because uploading is free for us to run.
- Offline-capable is not the same claim as browser-based: Tabreon tools require an initial page load, but the processing itself does not depend on a round trip to a server.