Passport Photo Service With Preview

Quick checklist

Use this short list to decide whether the current photo is worth continuing with.

• Confirm whether your question is about rules, image size, digital upload, photo code, or print output.
• Use a clear source photo with enough room around the head and shoulders.
• Check the preview before checkout instead of paying for a weak source image.
• Use official GOV.UK or HM Passport Office instructions for the final application step.

Step by step

Follow this sequence to keep the workflow clear and reduce avoidable mistakes.

1. 1

   Identify the photo task

   Decide whether you need a rule explanation, a digital file, a photo code, or a printable output.

2. 2

   Check the source image

   Look for obvious rejection risks such as blur, strong shadows, glare, tight crop, or busy background.

3. 3

   Use the preview-first route

   Open the checker or main online service and continue only if the prepared preview looks suitable.

4. 4

   Choose the correct output

   Use digital, code, or print-ready guidance based on what the application route actually asks for.

Common mistakes

These are the errors most likely to waste time or trigger a preventable rejection.

• Treating a digital upload file, photo code, and printable sheet as the same output.
• Assuming size alone means the photo will be accepted.
• Uploading a close selfie that leaves no room for a compliant crop.
• Ignoring photo handling, support, and refund information before checkout.

What to check in the preview

The page should give practical evaluation steps, not just sell the feature.

• Check that the head is not too close to the edge.
• Check the background is plain and evenly lit.
• Check the eyes are visible without glare or shadow.
• Check the output route before payment.

Preview-first service reduces uncertainty before checkout

Preview-first wording is a trust signal because users can understand the prepared image before deciding whether to continue.

• A preview helps users see crop, background and framing before final output.
• Warnings should not be hidden behind a progress bar or checkout step.
• Preview does not guarantee official acceptance, but it helps reduce obvious risk.
• The user still needs to choose the correct output route after preview: digital, code or print.

What preview should and should not mean

Clear preview expectations reduce support issues and improve trust.

• Preview means seeing a processed version of the source photo.
• Preview should not imply official approval.
• Preview should show warnings when the source photo may need a retake.
• Preview should help the user decide whether to continue, not force payment first.