Editorial policy

Anfas.Pro publishes verified photo requirements for government-issued documents. Our content is used by people whose travel plans, residency status and livelihoods depend on getting these details right. Here is how we keep that responsibility.

Source-first

Every document specification on this site is traced to a primary source: an authority website, an official PDF, an embassy notice, or an ICAO 9303 reference where no national rules are published. The source URL and verification date are visible on each leaf page.

We do not paraphrase from competitor sites. Where we cite a number, we either reproduce the authority's exact phrasing or convert units explicitly (mm ↔ pixels at the declared dpi).

How each page is checked

Every document page is checked by the Anfas.Pro editor against the official page of the authority that issues the document. The link to that page is on the document page, next to the date of the last check.

We check what decides whether a photo is accepted: the photo size, the head height, the background and, for online applications, the file — its size in pixels, its weight and its format.

Authorities publish different amounts of detail, so a page follows its source in one of four ways:

Checked word for word: the authority publishes exact figures, and the page repeats them.
The authority’s general rules: the authority describes the photo in words (“plain light background”, “no shadows”), and we turn the description into measurable sizes.
Partly: the authority publishes only part of the requirements, for example the photo rules without the size.
The ICAO standard: the authority publishes no figures of its own, so the page follows ICAO 9303, the international standard for travel-document photos, and says so.

Found a mistake? Write to hello@anfas.pro with the page address and the source you found.

Where the rejection reasons come from

Document pages list the typical reasons a photo is rejected and what to change. Every entry in our data carries a note of its origin, and that note decides how the page shows it:

Published by the authority: the reason and the fix follow the material the authority itself has published. The page prints a code next to the reason only when every entry in the list carries this note — at the time of writing, a handful of lists.
Restated from a published rule: the authority publishes a rule (for example "no glasses") but no code. The page puts the rule in plain words — what is wrong and what to change — with no code, and the list says so.
Common failure without a published rule: a usual reason a document photo is rejected, checked against the authority's requirements. Shown the same way, with no code. Any working label we keep for such entries stays in our data for cross-referencing: it is never printed and never presented as an authority's code.

Automated quality gates

Six checks run before every build, with two more available on demand:

npm run check — schemas, links, snapshots, redirects, sitemaps, jargon, meta budgets.
check:a11y — WCAG 2.1 AA via axe-core (10 representative pages).
check:cwv — Lighthouse Core Web Vitals against a 9-page sample.
check:translations — fails build if any declared locale falls below 100 % label/spec coverage.
check:localization — strict per-locale coverage + lint (numeric specs preserved, code IDs preserved, no Cyrillic in non-Cyrillic locales).
check:sources — HTTP liveness of every cited authority URL.
check:freshness — flags profiles where the reviewer-log entries reference only secondary (non-gov) sources, or where the last check is more than a month old.
check:consistency — flags drift between the narrative dimension claims (e.g. "40×60 mm") and the underlying printSpec (which drives the photo generator).

Build-time locale gating: any locale below 80 % translation coverage is automatically excluded from publishedLangs — meaning no HTML is generated for that locale, no sitemap entry is emitted, and no hreflang tag points to it. This prevents mixed-language pages from reaching Google.

Freshness and corrections

We re-check a profile when a country publishes new rules or a reader reports a change, and every month we check the requirements against the official sources. The date of the last check is shown on every page and in our sitemaps. When the source confirms a reader’s report, we correct the page.

What we do not do

No AI-generated content without expert review. Every page is read end-to-end before publishing.
No image retouching that changes biometric features. Our tool normalises framing, background and exposure — it does not alter facial geometry.
No advertising or sponsored placement on document specification pages.

Daha az yaygın ama doğrulanmış belge formatları

Bu ülkeler için Anfas.Pro üzerinde üçten az doğrulanmış özellik bulunuyor. Aşağıdaki her bağlantı; tam boyutu, arka planı, baş oranını ve özelliğin dayandığı resmi kaynağı içeren ayrıntılı bir sayfaya yönlendirir.