How to fix "identity verification failed — blurry photo" on Crypto.com?

Understanding the Blurry Photo Error

1. The system rejects submissions when facial features, document edges, or text cannot be clearly distinguished due to motion, poor focus, or low-resolution capture.

2. Crypto.com’s identity verification engine applies strict optical character recognition (OCR) and liveness detection protocols that require pixel-level clarity for both ID documents and selfie frames.

3. Lighting inconsistencies—such as strong backlighting, shadows across the face, or glare on ID surfaces—introduce noise that degrades image fidelity before processing begins.

4. Camera lens smudges, screen reflections during document placement, or zooming in digitally rather than capturing at native resolution all contribute to irreversible loss of detail.

5. Automatic cropping by mobile OS camera apps may unintentionally cut off document corners or truncate facial landmarks essential for biometric alignment.

Device-Specific Capture Guidelines

1. Disable HDR mode on iOS devices, as it merges multiple exposures and blurs fine text on passports or national IDs.

2. On Android, turn off AI-enhanced shutter modes and use “Pro” or “Manual” camera settings to lock focus and exposure before shooting.

3. Avoid using front-facing cameras for ID uploads; their lower megapixel count and fixed focus often fail OCR validation thresholds.

4. Do not hold the document against a glossy surface—glass tables or smartphone screens create specular highlights that obscure characters.

5. Place the ID flat on a matte, solid-color background like a white notebook cover or unprinted cardboard to maximize contrast and edge definition.

Document Preparation Requirements

1. Ensure all four corners of the ID are fully visible and unobstructed—no fingers, tape, or folded edges within the frame.

2. Remove protective film from plastic ID cards; static charge attracts dust particles that appear as micro-blurs under high-magnification review.

3. For passports, open to the data page only—do not include visa stamps or observation pages, which confuse layout parsing algorithms.

4. If your ID contains holographic elements, position it perpendicular to the camera lens to minimize diffraction artifacts that mimic motion blur.

5. Confirm expiration dates and issue numbers are legible without digital enhancement—Crypto.com does not accept screenshots or edited images.

Selfie Verification Best Practices

1. Maintain neutral facial expression with eyes fully open and mouth closed—smiling distorts jawline geometry used in 3D depth mapping.

2. Remove hats, sunglasses, and scarves; even translucent fabrics interfere with infrared-based liveness checks on supported devices.

3. Hold the phone at eye level, not above or below, to prevent perspective distortion of nasal bridge and orbital structure.

4. Use natural daylight near a window instead of artificial lighting—LED bulbs often emit inconsistent color temperatures that skew skin-tone analysis.

5. Do not apply real-time filters, beauty modes, or AR effects; these alter pixel values in ways that invalidate cryptographic hash matching.

Frequently Asked Questions

Q: Can I upload a scanned PDF instead of a photo? No. Crypto.com only accepts JPEG or PNG files captured directly via device camera. Scanned documents trigger automated rejection due to metadata anomalies and interpolation artifacts.

Q: Why does my government-issued ID pass OCR but fail liveness check? Liveness detection analyzes micro-movements, texture gradients, and reflection patterns unique to live human tissue. Flat printed surfaces lack subsurface scattering properties required for validation.

Q: Does wearing prescription glasses cause blurry photo failure? Yes—if lenses reflect ambient light or have anti-glare coatings that scatter photons unevenly. Remove them for the selfie unless medically necessary; in that case, tilt head slightly downward to reduce reflection hotspots.

Q: Is there a file size limit that affects sharpness? Uploads must be between 100 KB and 8 MB. Files under 300 KB often indicate heavy compression; over 5 MB may contain redundant EXIF data that interferes with preprocessing pipelines.