Convert a PNR From a Screenshot or Photo — No Typing Required

Sometimes the raw PNR text just isn't available to copy. A colleague forwards you a WhatsApp screenshot of a booking. A client sends a photo of a printed confirmation. An old itinerary only exists as an image buried in an email thread from months ago. In every one of these cases, typing out the PNR by hand — character by character, guessing at a smudged digit or a cut-off line — is the only alternative. Screenshot upload removes that step entirely.

How to Use It

1. Open Advanced Tools & SettingsOn the PNRGenius homepage, below the Convert button.
2. Upload the screenshot or photoAny clear image of the raw GDS booking text.
3. Review the extracted textThe text pulled from the image lands in the same box you'd normally paste into — give it a quick glance before converting.
4. Click ConvertSame result as pasting the text yourself: a full, structured itinerary.

Where This Actually Gets Used

• Forwarded screenshots. A colleague or client sends a booking as an image rather than text — common in WhatsApp-heavy workflows.
• Old or printed confirmations. A booking that only exists as a photo of a printed page or an old screen capture.
• When you're away from the GDS. A quick photo of a screen is sometimes faster to capture than logging in to pull the raw text, especially from a phone.

What Makes a Screenshot Easy (or Hard) to Read

Text extraction quality depends almost entirely on the source image, and a few habits make a noticeable difference:

• Crop to just the booking text. A tight crop of the flight segment lines reads more reliably than a full desktop screenshot with the PNR shrunk down in the corner of a much larger window.
• Shoot straight-on, not at an angle. A photo taken at a steep angle to the screen distorts the monospace character spacing GDS terminals rely on, which is exactly what makes columns line up correctly in the first place.
• Watch for screen glare. A phone photo of a monitor picks up glare and reflection far more easily than a direct screenshot — if a photo is the only option, angling the shot slightly to dodge overhead lighting helps.
• Resolution matters more than color. A crisp black-and-white screenshot extracts more reliably than a blurry color one; sharpness of the individual characters is what counts.

When a PNR Spans More Than One Screen

A long PNR — a big group, or one with a lot of remarks and fare notes — sometimes doesn't fit in a single screen and ends up captured as two or three separate screenshots. The straightforward approach is to upload each screenshot, review the extracted text from each, and combine them into one block in the correct order before converting. If the multiple screenshots actually represent separate PNRs rather than one long one, pasting each extracted block into Batch / Group Mode with a separator line between them is usually faster than converting each one individually.

Either way, it's worth checking the seam between screenshots carefully — a segment line that got cut in half across two captures is the one thing OCR can't reliably reconstruct on its own, since half the line simply isn't in either image.

OCR Mix-Ups Worth Double-Checking

GDS terminal fonts are monospace and fairly OCR-friendly compared to handwriting or stylized fonts, but a handful of character pairs still get confused on lower-quality images: a capital O versus a zero, a capital I versus a lowercase l versus the digit 1, and three-letter city or airport codes that differ by a single character.

// as extracted, worth a second look:
2  DL 45 H l0SEP 1*ATLLHR HK1  945P 1105A/11SEP
// "l0SEP" — is that a lowercase L or the digit 1?

None of this is a reason to distrust the feature — it's a reason to do exactly what the review step is there for: a quick scan of the extracted text against the original image before hitting convert, rather than assuming every character came through perfectly.

Where the Image Goes

The uploaded image is used to extract the PNR text you're converting. If you want the specifics of how images and other data are handled, that's covered in the Privacy Policy rather than repeated here.

Scanned Confirmations and Printed Documents

Not every source image is a screen capture. A printed itinerary that only exists as a photo or a flatbed scan brings its own quirks — paper texture, slight curling near the edges of a page, a staple mark cutting across a line of text. These generally extract just as reliably as a screenshot as long as the print itself is legible, but a couple of habits help: lay the page as flat as possible before photographing it, and make sure the crop includes full lines rather than cutting text off at the page margin, since a line truncated mid-flight-number is the one thing no amount of image quality can fix after the fact.

Old printed confirmations are also more likely to use a different, non-GDS layout than a raw PNR — some airline-issued itinerary receipts format flight details as prose rather than the compact GDS line format. Extraction still works on these, but the resulting text won't look like a typical PNR, so it's worth reading it over rather than expecting the familiar segment-line shape.

When Extraction Comes Out Garbled

Every so often an image is too blurry, too low-resolution, or too oddly lit for reliable extraction, and the text that comes back is visibly wrong — missing characters, scrambled flight numbers, whole lines dropped. When that happens, the fastest fix usually isn't fighting with the same image. Retaking the photo with better lighting or a closer crop, or going back to whoever sent the screenshot and asking for the original booking confirmation as text, resolves it faster than trying to hand-correct heavily garbled output.

For a partially garbled result that's mostly readable, the extracted-text box is fully editable before conversion — correcting one or two misread characters directly in the box, then converting, is often quicker than starting over with a new image entirely.

Screenshot Upload vs. Retyping by Hand

Retyping a PNR from an image means reading dense, unfamiliar monospace text character by character and transcribing it correctly — a task that's more error-prone than it sounds, since a single mistyped digit in a flight number or date can silently produce a wrong itinerary that looks entirely plausible until someone checks it against the original. Screenshot upload doesn't remove the need for a final check, but it shifts the task from blind transcription to verification — comparing the extracted text against the image is faster and less mistake-prone than typing the whole thing out from scratch.

This matters most on longer or messier PNRs: a short, clean single-segment booking is quick to type either way, but a group PNR with a dozen segments, remarks, and SSR lines is exactly where manual transcription both takes the longest and carries the highest chance of a small, easy-to-miss error slipping through.

Screenshots of Group Bookings

A single screenshot sometimes captures an entire multi-passenger PNR — a family of four or a small group all sold under one record locator, with every name and segment visible in one image. In that case, upload and extraction work exactly the same way as for a single-passenger booking; the whole block of text comes back at once and converts as the one group PNR it actually is.

It's a different situation when a group is split across several separate PNRs, each captured in its own screenshot — a common outcome once a party is larger than a GDS allows in a single record. Extract each screenshot individually first, then hand the resulting text blocks to Batch / Group Mode rather than converting them one at a time; that combination covers both problems a paper-and-screenshot-heavy group booking tends to create — no raw text to copy, and too many separate bookings to convert by hand one by one.

Same Converter Underneath

Once the text is extracted, everything else works exactly like the standard converter — GDS auto-detection, layover calculation, PNR Health Check warnings, PDF export, translation into 25+ languages. The screenshot upload only changes how the text gets into the box, not what happens once it's there.