Contact Passport-Photo.co.uk Support

Quick checklist

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

• State whether the issue is about upload, payment, download, or photo quality.
• Include the email address or order details used in the purchase if relevant.
• Attach screenshots or rejection messages when they help explain the problem.
• Check privacy, refund, and terms pages first for policy-specific questions.
• Use the help page for common upload, checkout, download, and photo-code questions.

Step by step

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

1. 1

   Identify the type of problem

   Knowing whether the issue is technical, billing-related, or photo-quality related makes the first support response more useful.

2. 2

   Gather the key details

   Include your email address, order details, and screenshots when they help support identify the issue quickly.

3. 3

   Email support clearly

   Send the summary to support@passport-photo.co.uk with a short, direct explanation of what you expected and what happened instead.

4. 4

   Use the policy pages when relevant

   Privacy, refund, and terms pages can answer many operational questions without delay.

5. 5

   Use the help page first for common issues

   The help page covers upload, payment, download, photo-code, print-sheet, and refund questions in one place.

Common mistakes

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

• Sending a vague message with no order or email details.
• Leaving out screenshots when the issue is visual or technical.
• Using support for questions already answered on the policy pages.
• Describing the application problem without explaining what happened on the site.

Contact support: include the right information

The contact page should help support resolve order and photo-output questions faster.

• Include the order email or order reference if the question relates to a paid order.
• Explain whether the issue is with a digital file, photo code, print-ready sheet or download.
• Attach only evidence that helps explain the issue, such as a rejection message or screenshot.
• Do not send unnecessary extra identity documents unless support specifically asks for relevant evidence.

What support can and cannot help with

Clear support boundaries improve trust and reduce frustration.

• Support can help with this website, delivered outputs, downloads and route-choice questions.
• Support cannot decide official passport application outcomes.
• Support cannot control government processing times or identity eligibility.
• If the question is about official application status, use the official application route.

What to include in a support request

Support pages are trust pages; they should tell users how to get a useful answer quickly.

• Order reference or payment email.
• Which output failed: digital download, print sheet or passport photo code.
• Screenshot or wording from the application step when relevant.
• Whether the issue is a download link, code recognition, photo quality or wrong output route.

Common support paths

This helps users self-route before sending a message.

• Use code support when a passport photo code is not recognised.
• Use download support when a paid file link fails.
• Use refund/remake review when the output appears wrong or unusable.
• Use requirements pages before uploading a new source photo.

When to use help pages before contacting support

Good internal routing can reduce support load and improve user confidence.

• Use photo code troubleshooting for code-route issues.
• Use rejected-photo pages for photo-quality problems.
• Use photo handling pages for privacy or file-handling questions.
• Use refund/remake review for order-support expectations.