Faded/Crumpled Receipts

There's a receipt at the bottom of the glovebox that's been through a summer and half a winter. The paper has gone soft. The thermal print has faded to a pale gray ghost of itself. Someone folded it in a wallet at some point, so there's a crease running straight through the total. You need the numbers off it anyway.

Faded receipt data extraction gets harder as the source document degrades, but "harder" isn't the same as "impossible." Glyf still reads damaged and low-contrast receipts. The question is how much usable signal is left on the page, and a few minutes of prep before you upload can move a borderline receipt from unreadable to workable.

Why thermal paper turns against you

Thermal receipts print by applying heat to a coated surface, and that same coating keeps degrading after the print job is done. More heat, sunlight, or friction darkens or fades it further. A receipt that sat in a hot car for a week looks noticeably worse than one printed yesterday, and a crumpled fold breaks the flat surface the text was printed onto, distorting the shape of characters right where a crease crosses them. None of that is a flaw in your phone or your scanning habit. It's just what happens to a specific kind of paper over time, and it's exactly why "faded and crumpled" gets its own guide instead of a footnote on general photo tips.

Flatten the paper before you flatten the photo settings

Fix what's physically wrong with the receipt before touching your camera. Smooth out folds by hand, press the receipt against a flat surface for a few seconds, and let curled edges relax instead of holding the paper in one hand while shooting one-handed with the other. That combination almost guarantees a soft, uneven image. If the receipt is torn along a fold, lay it flat and let the pieces sit close together rather than trying to hold them in alignment mid-shot. A receipt that's physically flat gives the camera one plane to focus on, instead of several angled surfaces competing for the same shot.

What faded receipt data extraction needs to work

A faded receipt is fundamentally a visibility problem, and light is the tool that fixes it. Even, indirect lighting (near a window rather than under a single overhead bulb) brings out more contrast between the print and the background than a direct flash, which tends to wash out already-faint text. If the bottom third of the receipt (where totals usually sit) looks noticeably lighter than the rest, that's worth a second shot from a slightly different angle before you upload rather than after. Supported formats are PDF, JPG, PNG, and WEBP, and Glyf validates file type and size in the browser the moment you add a file. A low-quality but valid image will still upload; it's contrast and legibility that determine how much comes back afterward.

What happens when the read is genuinely uncertain

When a document is too degraded for the Data Extraction Engine to confidently read a critical field, that document gets automatically flagged as "Needs Attention" rather than filled in with a guess. That flag triggers on missing invoice number, date, total cost, currency, issuing company, category, short description, or line items, the fields that matter most for the record to be usable. A faded receipt with an unreadable total is a textbook case: rather than a fabricated number sitting quietly in your export, you get a flagged document in a dedicated review queue, accessible from the Dashboard, where you can open the original image next to the extracted fields and fill in what the engine couldn't confidently read.

Prioritize what the record actually needs

You're not trying to preserve every faint decorative line on a damaged receipt. Focus your prep and your review on merchant name, date, total, tax, and any tip or line-item detail you'll actually need later. If those specific areas are legible, the receipt has a reasonable shot at becoming a usable record even if the rest of the page looks rough. If the bottom section (where totals typically live) is a lost cause, that's usually the point where retaking the photo beats trying to extract from what you have.

Don't crop tight on a damaged receipt

Cropping aggressively is risky on any receipt and worse on a damaged one, because you can't always predict where the useful information survived. A faded corner might be hiding a subtotal you'd otherwise have caught. Leave visible margin on all sides (top, bottom, and both edges) so the full structure of the document stays in frame even where it looks unimportant. For general framing and lighting fundamentals beyond damage-specific fixes, see Receipt Photo Best Practices.

When you have options, use the best one

If you're holding a faded paper copy and also have a digital confirmation email, upload the digital version. If you took three photos and one is noticeably sharper, use that one. If the original paper is still around and the first photo came out rough, a second attempt costs you thirty seconds and often beats trying to rescue a bad image after the fact.

For related image-quality context, see the accuracy hub or the wider receipt extraction workflow.

FAQ

Will a faded receipt always get flagged as Needs Attention? Only if a critical field (like total cost, date, or issuing company) can't be read with confidence. A faded receipt with a legible total and header can still extract cleanly.

Is there a limit to how damaged a receipt can be before it's rejected outright? Glyf validates file type, size, and duplicates before upload, not visual quality. A valid PDF, JPG, PNG, or WEBP under 10MB will always be accepted for analysis. It's the extraction results, not the upload step, that reflect how readable the receipt actually is.

Should I retake a photo or just fix it in review afterward? Both work. Retaking a photo before upload usually saves review time later, but if a field comes back wrong or missing, you can correct it directly in the Invoice Drawer without re-shooting anything.