LocalUtils
Local tools with a visible boundary
Last updated: July 14, 2026
LocalUtils is a focused set of browser utilities for people who want to inspect or transform a file without first sending that file to a processing server.
The processing boundary
The selected file is passed to browser-side libraries such as PDF.js, PDF-lib, piexifjs, heic2any, Papa Parse, Tesseract.js, and the Web Crypto-compatible hashing code used by each tool. Different tools use different techniques; we do not claim that every operation uses WebAssembly or a Web Worker.
Storage on your device
Most working data lives in page memory. The JSON formatter stores its current input and scrub preferences in localStorage, and the PDF toolbox stores its queue in IndexedDB so a refresh does not immediately discard it. These stores belong to your browser profile and should be cleared on a shared device.
Services that use the network
The application still downloads code and language assets. Optional account authentication uses Supabase, billing flows use Stripe, and advertising may use Google services. Those connections are separate from the file-processing path; the tools do not post selected file contents to them for conversion or analysis.
Verify instead of trusting a slogan
Open the browser developer tools and watch the Network panel while processing a test file. After the application and any required OCR assets have loaded, you can also disconnect the network and repeat the operation. Account, billing, advertising, and first-time asset downloads will not work offline.
Limits and feedback
Browser processing reduces data transfer; it does not guarantee legal compliance, perfect output, or protection from a compromised device or extension. Review every result before relying on it. Signed-in users can report a problem or suggest an improvement with the Feedback control in the sidebar.