# How it actually works.

> How QR codes, image tools, PDF tools, the shareable note and developer tools actually work under the hood — one explainer per family, mechanism by mechanism.

Canonical: https://stayslocal.app/how-it-works
Last updated: 2026-08-13

Every family here works a specific, checkable way — not “processed securely,” but the actual codec, the actual file format, the actual API. Pick one.

- [What is actually inside the square.](https://stayslocal.app/how-it-works/qr): A QR code is not a picture of a link. It is text, encoded into a grid with enough redundancy to survive being crumpled, badly lit, and photographed at an angle. Here is how that works, and what each type of code really contains.
- [What actually happens to your photo.](https://stayslocal.app/how-it-works/image): Compressing, resizing or cleaning up a photo usually means uploading it somewhere first. Here it does not. Here is the actual mechanism — decode, edit, re-encode — and what it guarantees.
- [What actually happens to your document.](https://stayslocal.app/how-it-works/pdf): Merging, splitting or watermarking a PDF usually means uploading a contract, an invoice or an ID scan to a site whose business model you have never examined. Here it does not — and the structural approach that makes that possible also produces a better file.
- [Where the note actually lives.](https://stayslocal.app/how-it-works/note): There is no database behind the shareable note, and no account. The note is the mechanism: it lives entirely inside the link you share. Here is exactly how that works.
- [Why it is safe to paste a real secret here.](https://stayslocal.app/how-it-works/dev): Developer tools are where secrets get pasted — an access token into a JWT decoder, a webhook signing key into an HMAC generator. Here is exactly what happens to them, mechanism by mechanism, so that claim is checkable rather than a promise.
