gotool.app · Privacy-first micro-utilities

Open-Source Micro-Utilities for Modern Workflows.

Completely client-side, privacy-first developer and business tools running at the edge.

No sign-up  ·  No uploads  ·  No tracking

Knowledge base

Field guides for practitioners

Long-form, no-fluff explainers on the algorithms, standards and engineering decisions behind everyday utility software. Written to be read — not skimmed.

Image Optimization

Understanding Client-Side WebP Image Compression Algorithms

How VP8 intra-frame prediction and entropy coding shave 25–35% off image weight — and why the entire pipeline can run inside your browser tab. A practical tour for developers.

Read Guide

QR Codes

How QR Code Error Correction Keeps Damaged Codes Scannable

Reed–Solomon parity codes let a QR symbol survive up to 30% damage and still scan instantly. We break down the four ECC levels — and when each one earns its keep.

Read Guide

Developer Tools

JSON Validation & Formatting: The Anatomy of Structured Data

One stray trailing comma can bring an entire integration down. Learn how JSON parsers actually work, which errors they catch, and how schema validation enforces structure.

Read Guide

Unit Conversion

The Mathematics of Unit Conversion: Precision, Rounding & Standards

A $125-million Mars spacecraft was lost to a unit mix-up. From SI base units to IEEE 754 rounding artefacts — here is what correct conversion actually takes.

Read Guide

Document Security

Digital Signatures Explained: Hashing, Key Pairs & Document Integrity

A digital signature proves who signed a document and that not a single byte has changed since. Hashing, key pairs and PKI trust chains — minus the maths degree.

Read Guide

Privacy Engineering

Why Client-Side Processing Is the Future of Privacy-First Software

The safest database is the one that never receives your data. The engineering case for moving computation to the edge — and the honest limits of the approach.

Read Guide

Tool ecosystem directory

Five focused subdomains, one shared engine

Each Gotool utility ships as its own lightweight subdomain with a single job done exceptionally well. They share one design system, one privacy protocol and one promise: your files stay on your machine.

  • qr.gotool.app In build
  • img.gotool.app In build
  • json.gotool.app In build
  • convert.gotool.app In build
  • sign.gotool.app In build

Roadmap status is published openly. Every chip becomes a standalone app — under the same zero-upload guarantee.

Core privacy protocol

Your data never leaves the browser tab

Every Gotool utility is compiled to run exclusively inside your browser engine using client-side JavaScript and WebAssembly. Files are read into memory, transformed locally, and handed straight back to you.

  • Zero server retention — there is simply nothing stored, because nothing is sent.
  • No accounts, no sessions, no telemetry attached to your work.
  • Once loaded, tools keep working offline; the network is optional.
  • Open-source code you can audit before you trust it.

The full contract is in our Privacy Policy and Cookie Policy.

About Gotool

Small tools. Serious engineering.

Gotool exists because most “free” web utilities quietly ship your data to a server: your screenshots, your contracts, your JSON payloads. We invert that model. The software travels to your data — never the other way round.

Alongside every tool we publish the theory behind it, so you understand exactly what happens to your files and why the results are trustworthy. No dark patterns, no sign-up walls, no surprises.

6In-depth field guides
5Tools in active build
0Bytes stored on servers