Your signature is a legal artifact. We never see it.
Compressed locally to 5–20 KB. Auto grayscale, paper-noise cleanup, white background out. Processed entirely in your browser.
Your file stays on your device. Compressed locally via WebAssembly.
Verify it yourselfDrop your image here
JPG · PNG · WebP · HEIC · max 25MB
What exactly happens to your file?
Click to see the full data path. No surprises.
What exactly happens to your file?
Click to see the full data path. No surprises.
- 1
You drop the file
Browser reads the file from your local disk into a `File` / `Blob` JavaScript object. This is the standard browser File API — same as any web upload form, except we stop there.
No upload here.
Other tools insert an upload step at this point. We don't — there is no server endpoint in our codebase that receives file content.
- 2
Browser compresses it
WebAssembly modules + Canvas APIs run on your device. For PDFs we use pdfjs-dist + pdf-lib (both ~3MB lazy-loaded once). For images we use the browser's built-in JPEG/PNG/WebP encoders + a libheif fallback for older HEIC support. All execution happens in your browser process.
- 3
You download the result
The compressed blob lives in browser memory. When you click Download, the browser triggers a local file save. No HTTP request goes out — the only network calls during a compression are loading the engine (cached on first use).
Verify any of this for yourself: open DevTools (⌘ ⌥ I on Mac · Ctrl Shift I on Windows / Linux), open the Network tab, then run a compression. You'll see the engine load on first use, then nothing during the actual compression. We have a full live demo at /privacy/verify.
You just compressed without uploading.
Here's what you didn't do — and why it matters.
Online signature compressors uploaded your signature
A signature is a legal artifact — and most online tools route it through their server before compressing. Even with claimed deletion windows, your signature briefly sits on infrastructure you don't control.
FormReady processed your signature locally
Grayscale conversion, threshold cleanup, and JPEG encoding all ran in your browser. The signature image never touched our servers — and the actual ink stroke is unchanged, only background noise was cleaned.
Our promise — verifiable
Four architectural commitments. Every one provable.
No upload endpoint
Our codebase contains zero server routes that receive file content. Architectural, not policy.
Audit the routesOpen-source compression engine
Fork it, audit it, run it offline. We open-source the compression logic under MIT.
View on GitHubNo file fingerprinting
We don't log file names, hashes, sizes, or any derived metadata. We log nothing about your file.
Read the privacy policySelf-verifiable
Every claim above is checkable by you in 30 seconds, in any modern browser, with the built-in DevTools.
Run the live demoCommon use cases
Common signature specs
Indian government exams use one of a few standard sizes. Match yours and use the suggested KB.
SSC CGL signature
SSC + IBPS share this spec
140×60 px · 10–20 KB
Open guideNEET / JEE signature
NTA portal · medical / engineering
140×60 px · 4–30 KB
Open guideIBPS PO signature
Banking entrance exams
140×60 px · 10–20 KB
Open guideGATE signature
Engineering postgraduate entrance
250×80 px · 5–150 KB
UPSC signature
Civil Services Examination
350×350 px · max 300 KB
Open guideCTET signature
Teacher eligibility test
140×60 px · 4–30 KB
FAQ
Why a separate signature tool?
Generic image compressors fail at the 5–20 KB range government forms demand because they treat signatures as photos. We treat signatures as line art: aggressive JPEG compression, grayscale, threshold cleanup of paper noise, white background. The result hits 10 KB while staying perfectly legible.
A signature is a legal artifact. Is it really safe to compress here?
Yes — safer than anywhere else online, in fact. Your signature image never leaves your browser. There is no server endpoint that receives it. Compressing your signature on a stranger's server (the way most online tools work) is a real liability — ours doesn't. Verify zero-upload yourself at /privacy/verify.
What does the cleanup step actually do?
Two passes: (1) grayscale conversion — replaces RGB with luminance; (2) binary threshold — pixels brighter than ~78% of white become pure white, darker pixels stay dark. This removes paper noise (yellowed paper, faint lines, shadows) while preserving your ink stroke. The actual ink path is not modified.
My signature was photographed against newspaper / lined paper. Will cleanup work?
Threshold cleanup whitens any pixel above ~78% brightness — it handles standard white paper, lightly-yellowed paper, and most printed lines well. Heavily-printed backgrounds (newspapers, grid paper) may need manual cropping first; some imperfection in the background may remain.
My signature is light / pencil. Will it survive?
Light pencil signatures may get partially erased by threshold cleanup. If so, scan or photograph again with a black ink pen and retry. We don't support contrast-boosting in v1.
Can I keep transparent background?
Not in v1. Most form portals reject transparent PNGs and want a white background JPG. PNG-with-transparency support is on the roadmap.