Free PNR Converter: How to Convert Any GDS PNR Instantly

If you work with flight bookings, you've probably had to take a raw GDS PNR and turn it into something a client can actually read. Doing this by hand — typing out airport names, calculating layover times, formatting dates — eats up time you don't have. This guide shows you how to convert any PNR into a clean itinerary in under 10 seconds, completely free.

What You Need Before You Start

All you need is the raw PNR text from your GDS. This works whether you're pulling it from Amadeus, Sabre, Galileo, Worldspan, or a compact/Smartpoint-style export — most converters, including PNRGenius, auto-detect the format so you don't need to tell it which GDS you're using.

Step 1: Copy the Raw PNR Text

From your GDS terminal, copy the full PNR display — passenger names, all flight segments, and any reference lines. You don't need to clean it up first; a good converter handles messy spacing, lowercase text, and irregular line breaks automatically.

1.SMITH/JOHN MR
3 BA 284 H 15JUL 2*LHRJFK HK1 1120A 215P 15JUL E
4 BA 179 T 25JUL 5*JFKLHR HK1 745P 750A 26JUL E

Step 2: Paste It Into a PNR Converter

Open PNRGenius (or any PNR converter tool) and paste the text into the input box. A good converter will:

• Auto-detect the GDS format
• Identify all passengers and their titles
• Resolve airline and airport codes to full names
• Calculate real flight durations — correctly accounting for time zones and daylight saving time
• Detect layovers and connection times automatically

Step 3: Click Convert

Within a couple of seconds, you'll get a structured itinerary card showing each flight segment with departure and arrival times, airport names, layover durations, and booking status — formatted so a client can understand it at a glance, without needing to know what "HK1" or "LHRJFK" means.

Step 4: Share It

Once converted, you can typically:

• Copy a clean text version to paste into an email or message
• Download a PDF for a polished, printable document
• Email it directly from your default mail client
• Translate it into the client's preferred language, if the tool supports it

Is It Really Free?

Yes — tools like PNRGenius are free with no signup, no credit card, and no per-conversion limits. There's no catch: you paste a PNR, you get an itinerary, and you can convert as many as you need.

What About Accuracy?

The biggest mistake free converters make is ignoring time zones — showing flight durations as a simple clock subtraction instead of accounting for the time difference between departure and arrival cities. A flight from London to Dubai that departs at 10:00 and "arrives" at 20:00 local time isn't a 10-hour flight; it's closer to 6-7 hours once you correct for the time zone difference. Make sure whichever tool you use handles this correctly, especially for long-haul or multi-segment trips.

How to Tell Which GDS a PNR Came From

If you work across multiple agencies or inherited a booking from someone else, you won't always know at a glance which GDS produced the raw text in front of you. A few visual cues make it easier to tell:

None of this matters for accuracy if you're using a converter that auto-detects the format — but recognizing the source system is still useful for spotting a mis-paste before you convert anything, and for knowing what "normal" looks like when something in the pasted text seems off.

How SSRs, OSI Lines, and Multiple Passengers Change What You're Pasting

A single-passenger, single-segment PNR is about as simple as raw GDS text gets. Real bookings usually aren't that clean. Add a second traveler and a couple of special service requests — a wheelchair request, a meal preference, a frequent flyer number — and the block of text you're copying grows considerably:

1.SMITH/JOHN MR  2.SMITH/SARAH MRS
3 BA 284 H 15JUL 2 LHRJFK HK2 1120 1415 15JUL E
4 SSR WCHR BA HK1 15JUL LHRJFK/P1
5 OSI BA FQTV BA998877/P2

The flight status (HK2) still applies to both passengers traveling together, while the SSR and OSI lines below reference one specific traveler using a passenger number. These special-request codes — WCHR for wheelchair assistance, FQTV for a frequent flyer number, and dozens more — are standardized across the industry, so they look and mean the same thing no matter which GDS generated the PNR; only the surrounding punctuation differs slightly. A good converter matches each SSR or OSI line back to the correct passenger automatically. Doing that by hand on a five- or six-passenger group booking with several special requests is exactly the kind of tedious, error-prone task a converter exists to remove.

Common Copy-Paste Mistakes, Regardless of GDS

• Copying a formatted itinerary view instead of the raw PNR. Several GDS interfaces offer a "pretty" graphical summary alongside the plain-text terminal display — the graphical version reads well for a human but isn't structured the way a converter expects, since it doesn't preserve the underlying segment syntax.
• Losing a line to word-wrap. Long segment lines can wrap onto two lines when copied through a remote desktop session or a narrow terminal window, splitting one flight's data across two lines of pasted text.
• Pasting a fare quote instead of a PNR. A fare display and a PNR display can look superficially similar at a glance; only one of them contains segment data a converter can work with.
• Capturing only part of a multi-page PNR. Bookings with many segments, remarks, or SSR lines often span more than one screen in a classic terminal — copying only what's currently visible leaves later data out entirely.
• Mixing tabs and spaces. Some terminal emulators substitute tabs for the fixed-width spacing GDS systems use natively, which can misalign columns once the text lands somewhere that doesn't preserve tab width.

Status Codes Beyond HK: What Else You Might See

Most PNRs you'll handle, regardless of GDS, show a clean HK for a confirmed segment. Occasionally you'll run into other two-letter codes, which follow the same convention across Amadeus, Sabre, Galileo, and Worldspan alike:

Seeing anything other than a plain HK is usually a sign that something changed after the segment was first booked — a waitlist clearing, an airline-initiated schedule change, or a reconfirmation — and it's worth double-checking the booking before sending a client an itinerary built on it.

Surface Segments (ARNK) and Split Bookings, Across Every GDS

Every major GDS — Amadeus, Sabre, Galileo, and Worldspan — uses a line called ARNK ("Arrival Not Known") to mark a gap between two flight segments that isn't a bookable flight at all: an overland transfer, a ferry crossing, or an open-jaw gap the passenger arranges independently. It carries no airline code, flight number, or status code, which is exactly why a converter needs to recognize it specifically rather than either erroring out or trying to calculate an impossible "layover" between two unrelated flights.

3 BA 284 H 15JUL 2 LHRJFK HK1 1120 1415 15JUL E
4 ARNK
5 AF 1780 Y 18JUL 3 CDGLHR HK1 1830 1905 18JUL E

It's also worth knowing that any GDS can split a booking into two separate record locators — commonly when one passenger in a group cancels, reroutes, or gets ticketed on a different schedule than the rest of the party. If a converted itinerary is missing a passenger you know was part of the original booking, the PNR was likely split rather than the converter having dropped something. Ask whoever sent you the PNR whether a second record locator exists for the rest of the party.

Troubleshooting: When a Paste Doesn't Convert Cleanly