Home About
About SnapPass
SnapPass does one thing: it turns a photo you already have into the exact photo a passport, visa or ID application demands — inside your browser, without sending the image anywhere.
Why it works this way
A passport photo is a biometric identifier. It is not a profile picture, and it is not something you can rotate the way you rotate a password. Yet almost every online photo service works the same way: you upload your face, a server stores it, processes it, and sends back a result. You have no way of knowing how long that copy lives, who can look at it, or what happens to it after the tool shuts down.
So this tool was built the other way round. Instead of asking how to make an upload secure, the question was how to avoid the upload. Background removal runs on a model compiled to WebAssembly; cropping, resizing, colouring and the print sheet are plain canvas operations. The result: the image never has an opportunity to leave the tab, which is a stronger guarantee than a promise about deletion.
How to verify the privacy claim yourself
Any claim about privacy should be checkable in under two minutes. This one is:
- Open the studio and let the page finish loading.
- Press F12 → Network tab → filter by Fetch/XHR.
- Load a photo and run the whole pipeline. You will see requests for the segmentation model, for anonymous usage counts, and — only if you have bought a licence — one call to validate that key. You will not see your image in any of them.
- Or simply disconnect from the network after the page has loaded. Everything up to and including the preview still works.
The honest footnote: the counter and the licence check do contact a server, and the segmentation model itself is downloaded once from a public CDN (jsDelivr and Google Cloud Storage) the first time you open the studio — those requests reveal your IP to those two providers, exactly as loading any web font would. What they never carry is the image: no photo, no filename, no thumbnail. If that matters to you, the privacy policy lists every request the page makes.
Where the numbers come from
34 documents, 13 requirement guides, one rule: every measurement on this site has to point at the issuing authority's own publication — a ministry, a passport office, an embassy, a border agency. Not another photo website, and not a summary of one.
Where two official sources disagree, the page uses the stricter value and says so. India is the clearest example: the Ministry of Home Affairs specifies an OCI photo on a plain light background that is not white, while several embassies publish looser pixel limits. The OCI page takes the tightest combination — 600 × 600 px, ≤200 KB, light grey — because a rejected upload costs you another appointment, and a wasted appointment is worse than an unnecessary padding of margin.
Rules also expire. Germany stopped accepting printed passport photos on 1 May 2025, which made a whole category of advice obsolete overnight. Pages affected by a change like that say it at the top rather than further down, because letting someone take a photo they cannot use is worse than telling them the tool is the wrong tool this time.
What we will not claim
- We do not guarantee acceptance. The final decision always belongs to the issuing authority. What this tool guarantees is the printed geometry and the background colour the authority publishes — nothing more.
- We do not claim hair-level precision. The segmentation model works at a resolution around 256 pixels. Fine flyaway hair against a busy background can leave a halo. A plain wall behind you is still the cheapest upgrade to your result.
- We do not edit faces. Nobody should look better in a passport photo than they do, and a tool that smooths skin would be helping you submit something the authority considers manipulated.
Who runs this
SnapPass is an independent project, not a company with a support department. It is built and maintained by Kuixiu Li, one developer who works on the principle that a file should stay where it was opened. It is funded by the $4.99 downloads — which is why there is no advertising, no account, and no reason to keep your data.
If a measurement on this site is wrong, or a rule has changed and the page has not caught up, write to support@snappass.org with the document and the source. Corrections are made on the page itself, not in a reply only you will read.
Page last reviewed: 19 November 2026.