Boarding passes are photographed constantly: gate excitement posts, expense-report attachments, itinerary shares with family. The barcode is easy to ignore because it looks like decoration under the flight number. It is not decoration. It commonly encodes passenger and booking data that a simple scan can reveal.
Use HideShot to cover the barcode, frequent-flyer number, and booking reference while keeping flight number, date, or gate visible if that is the point of the post. Everything runs in your browser on your device.
Guide
People post boarding passes for good reasons. A traveler wants to share that the trip is real. An employee attaches a pass photo to an expense report. A parent texts the family group so someone can track a connection. In each case the visible flight number and gate feel like the whole story. The barcode underneath is treated as noise.
That barcode is a machine-readable bundle. Depending on the airline and pass format, it can include a passenger name reference, a PNR or booking code, a frequent-flyer number, and other fields that help systems retrieve or modify a reservation. Security researchers and airlines have warned for years that casual photos of boarding passes can expose more than a destination hashtag. HideShot exists for the practical fix: open the photo, cover what a scanner would read, and keep the travel details you actually meant to share.
What a boarding pass barcode can encode — and why it matters
Modern boarding passes often use PDF417 or similar barcodes (sometimes QR) that airline and airport systems scan for check-in and boarding. Those codes are built for machines, not for Instagram. When the barcode is sharp in a photo, anyone with a barcode reader app can pull structured fields without guessing from the printed text.
A frequent-flyer number inside that payload is a long-lived identifier tied to your travel history and account. A PNR or booking reference can be enough, in some airline workflows, to look up itinerary details or initiate changes when combined with a name. Even when full account takeover is not trivial, the pass photo becomes an unnecessary leak of travel identity to followers, expense reviewers, or anyone who screenshots your story.
You do not need inventing threat theater to act on this. The conservative rule is simple: if a field is not required for the audience, conceal it. Flight number, date, and gate often are the social or logistical point of the image. The barcode usually is not.
What to blur on a boarding pass photo
Barcode or QR code. Cover the entire symbol, including margins. Partial coverage still leaves a scannable strip.
Frequent-flyer or loyalty number. Printed near the name or barcode on many passes. Black it out even if you keep the name visible for a family share.
Booking reference / PNR. Usually a short alphanumeric code. Hide it on public posts; for private family shares, decide deliberately whether they need it to help with the trip.
Optional keeps. Flight number, date, departure city, and gate are often enough for an excitement post or a “I’m on this flight” update. Passenger name may stay for a private expense attachment and should go for a public social post.
How to redact a boarding pass with HideShot
- Open the boarding pass photo on this page — drag it in, choose the file, or paste from the clipboard.
- Pick Black Box for the barcode and for any frequent-flyer or PNR text. Use Blur only if you want a softer look on non-critical background clutter.
- Draw over the barcode first, then the printed loyalty and booking codes. Check both the front of a mobile pass screenshot and any second page or wallet stub in the same image.
- Leave flight number, date, and gate visible if that is why you are sharing. Re-scan the frame for tiny repeated codes in headers or footers.
- Download the edited image, open it full size, and confirm the barcode is visually destroyed — not merely dimmed. Share only the edited file.
Common scenarios
Travel excitement posts. Gate selfies and “wheels up” stories do not need a scannable pass. Keep the flight number if you want; cover barcode, PNR, and loyalty numbers before the story is public.
Expense report submission. Finance teams need proof of travel dates and sometimes passenger name. They rarely need a live barcode in the attachment. Redact machine-readable codes and loyalty numbers; keep the fields your policy requires.
Sharing an itinerary with family. Relatives may need flight number, date, and arrival time. Send a redacted pass photo or a typed summary instead of a raw barcode-heavy screenshot that also sits in a group chat archive.
Common mistakes
Cropping the top of the pass but leaving the barcode. The code is usually near the bottom or side — cropping the header does nothing if the symbol remains.
Light blur on a high-contrast barcode. Barcodes are built to survive imperfect scans. Destroy them with a solid black region.
Redacting the barcode but leaving the printed PNR beside it. Text and code often carry overlapping data. Cover both.
Posting a mobile-wallet screenshot with notification banners. Status-bar alerts can show confirmation codes or email subjects. Scan the whole frame.
Keep the travel story — lose the scannable payload
A boarding pass photo can celebrate a trip without publishing a machine-readable booking bundle. HideShot lets you make that split in the browser: barcode and loyalty identifiers covered, flight context intact. Local editing means the original pass image does not need to travel through a remote service just so you can black out a rectangle.
For identity documents in the same travel folder, pair this habit with passport-number redaction and QR-code cover guides on HideShot — different documents, same rule: share the meaning, not the scannable extras.
If you travel with companions, remember that a group photo of several boarding passes multiplies the problem. Each barcode belongs to a different booking. Cover every symbol in the frame before the image sits in a shared album. The same care applies when a gate agent prints a new pass after a seat change — the replacement photo deserves a fresh redaction pass, because the new barcode still encodes booking data even when the flight number looks familiar.