Toolerax Reviews and Details

Questions & Answers

1. What makes Toolerax unique?

   Most of it does not run on our servers at all. 102 of the 169 tools process your file inside your own browser using JavaScript and WebAssembly, so the file is never uploaded — you can verify that yourself by opening the browser's Network tab while merging a PDF and watching for a request that never appears.

   The other 67 are honest about being different. Decoding HEIC, rendering a Word document or running OCR needs real desktop engines (LibreOffice, ImageMagick, Ghostscript, qpdf, Tesseract), so those run on a server over HTTPS and the file is deleted the moment the result is returned. Every one of those tool pages says so on the page rather than burying it.

   The second unusual thing is format coverage: alongside the usual PDF and image work, it handles EPS, XPS, TIFF, PSD, HEIC, AVIF, the OpenDocument formats, legacy Microsoft formats including Publisher, Visio, WordPerfect and Works, and Apple iWork files (Pages, Keynote, Numbers).

2. Why should a person choose Toolerax over its competitors?

   Three reasons, and one reason not to.

   No metering. Smallpdf applies a daily download limit to most tools on its free plan and iLovePDF caps tasks per tool; TinyPNG stops at 20 images of 5 MB each; remove.bg sells credits. Toolerax has no account, no watermark, no daily limit and no paid tier at all — mainly because two thirds of the tools cost nothing to run, since they run on your machine rather than ours.

   Files that must not be uploaded. If you handle contracts, medical paperwork or anything under an NDA, "we delete it afterwards" is not always good enough. For the 102 browser-side tools the file never leaves your device, which is a different category of answer.

   Breadth. 169 tools in one place: PDF, image, text, converters, calculators, developer and SEO utilities, including formats most converters skip (PSD, EPS, XPS, Visio, Publisher, WordPerfect, Apple iWork).

   And the honest counterpoint: if you need e-signatures, a visual PDF text editor, bulk automation, an API or mobile apps, the paid products do those and Toolerax does not.

3. How would you describe the primary audience of Toolerax?

   People with one file and one problem, who do not want to sign up for anything to solve it.

   In practice that is three groups:

   • Office and admin workers — merging a PDF, compressing a scan under an upload limit, converting a HEIC photo somebody emailed them, turning a photographed document into a PDF for a portal.
   • Anyone handling confidential paperwork — legal, medical, HR, finance. They are the reason the browser-side split matters: for those tools the file physically never leaves the machine, so using an online tool does not breach a policy.
   • Developers, designers and students — JSON and XML formatting, Base64, JWT decoding, hashes, cron expressions, colour and gradient tools, QR and barcode generation, plus calculators for EMI, BMI, GPA and compound interest.

   It is deliberately not built for teams or enterprises: there are no accounts, no collaboration and no admin console.

4. What's the story behind Toolerax?

   I build software for hospitals and diagnostic laboratories — hospital information systems, and the integrations that connect lab analyzers to the systems storing their results. That work produces a constant stream of awkward files: multi-page TIFF scans from document scanners, HEIC photos, manuals in formats nobody can open, reports that have to be converted before they can be emailed.

   Every time I went looking for a converter I found the same thing — a site that wanted an upload, then an account, then a subscription, and handed back a watermark. The uploading bothered me most. Merging two PDFs or resizing an image does not require sending patient paperwork to someone else's server; browsers have been able to do that work locally for years.

   So I started building the tools the way I thought they should work, one at a time, and published them free. Toolerax is the result: 169 tools, built and maintained by one developer, funded by ads on the pages rather than by metering the tools.

5. Which are the primary technologies used for building Toolerax?

   Frontend: Next.js with TypeScript and Tailwind CSS, deployed on Vercel. Every tool page is statically generated, which is why they load quickly.

   Browser-side tools (102 of 169): plain JavaScript, the Canvas API and WebAssembly. pdf-lib handles the PDF work, and the AI background remover runs an ONNX segmentation model through Transformers.js — WebGPU where the browser supports it, WebAssembly otherwise. None of these send the file anywhere.

   Server-side tier (67 tools): an ASP.NET Core 8 API on a Windows VPS, wrapping the open-source engines that actually do the work — LibreOffice for document conversion, Ghostscript for PDF compression and rasterising, ImageMagick with libheif for HEIC, PSD, TIFF and AVIF, qpdf for encryption and repair, and Tesseract for OCR. Each request gets an isolated workspace that is deleted immediately after the response.

   One library from the project is open source: github.com/toolerax/fancy-text (MIT).

6. Who are some of the biggest customers of Toolerax?

   There are none to name, and that is by design rather than modesty.

   Toolerax has no accounts, no sign-up and no paid tier, so there are no customers in the usual sense — nobody registers, nothing is billed, and for the majority of tools the file is processed in the visitor's own browser, so we do not even see what was converted.

   It is also a young site, launched in July 2026 and run by one developer. Anyone claiming a marquee customer list at this stage would be making it up.