Search for QR code scan history and you find two crowds looking for opposite things. One is a person trying to recover a code they scanned last Tuesday. The other is a business trying to learn how many people scanned the poster in the lobby. The records they want live in different places, and only one of them exists by default.
Two different questions, one phrase
The confusion is worth naming precisely, because it explains why so many answers to this question are unhelpful.
A person scanning is doing local work. The phone reads the square, produces a string, and hands it somewhere. Nothing in that sequence requires a record, and most of the time no record is created.
A code owner sits on the other side of a web request. If the code routes through a server they control, that server sees every hit and can count them. The log belongs to the code, not to the scanner, which is why a business cannot ask a visitor's phone anything and a visitor cannot ask the poster anything.
On iPhone, the record is your browser history
There is no list of scanned codes anywhere in the iOS Camera app. What happens is that the camera decodes the code, shows the address in a banner, and, when you tap it, hands the address to Safari or whichever browser is set as default. The trail you are looking for is that browser's history, in time order, on the day you were standing there.
That works well and breaks in three situations. If the code opened an app directly, a link that resolves into a social app or a maps app, nothing appears in the browser history at all. If the payload was not a link, a WiFi network, a contact card, a plain string of text, there was never a page to record; you get a saved network or a new contact instead. And if you read the banner and decided not to tap, the phone kept nothing, because nothing happened.
The Code Scanner in Control Center behaves the same way. It is a viewfinder, not a logbook.
On Android, the history lives in the Google app
The native camera readers on Pixel, Samsung and the rest behave like the iPhone one: decode, offer, forget. The address ends up in your browser history only if you opened it.
Google Lens is the exception, and it is the one worth checking. Lens is a search product, so a Lens scan is a search, and searches are recorded in your Google account activity when activity saving is switched on. A code read through Lens, or through the gallery's image analysis on many Android phones, can usually be found by scrolling back through your own activity history in the Google app rather than through anything in the camera. Scanning codes with Google Lens covers where those entry points sit, and notes the flip side of the same property: Lens recognition happens on Google's servers, which is exactly why there is something to look back through.
The code scanner tile in Quick Settings on recent Android versions keeps no list of its own.
Scanner apps keep a log, because that is what they are for
Third-party readers are the only tools in this list that treat history as a feature. Most keep a local list of everything they have decoded, with timestamps, and many let you star or rename entries. If you scan codes as part of a job, stock-taking, inspections, an event door, that list is the actual reason to install one rather than using the camera.
Three caveats before you rely on it. The log usually lives only on that device, so a reinstall or a new phone loses it unless the app syncs to an account, and an app that syncs your scan history to a server is making a privacy decision on your behalf that deserves reading about first. The app store is also full of decoders whose real business is advertising. And a reader that shows you the decoded text before it opens anything is the better instrument regardless of whether it keeps history; our QR code reader page explains why that ordering matters more than the feature list.
Why a camera scan often leaves nothing behind
It is tempting to read the absence of a history as a gap somebody forgot to fill. It is closer to the opposite.
Decoding a QR code is arithmetic performed on an image on your own device. No request goes out, no server is consulted, nothing is transmitted, and what happens when you scan a code walks the whole sequence. A camera app that logged every decode would be manufacturing a record of your physical movements that did not otherwise exist, storing it on the device, for no functional benefit. Not keeping it is a design choice, and a defensible one.
The consequence is simply that if you need a record you have to arrange for one in advance. Paste the link into a note when it matters, or use a reader that logs. There is nothing to retrofit.
And if you are hunting for something specific right now, the fastest route is usually sideways rather than through the phone: look for the destination's own record. An order confirmation, a login notification, a ticket sitting in an app, a network in your WiFi list. Whatever you scanned probably left a trace at the far end even though your camera kept none.
If you own the code, the log is on your side
Now the other crowd. If you printed the code, you are asking a different question, and the answer is architectural rather than a setting somewhere.
A code that encodes the destination directly sends the phone straight to that address. No intermediate server exists, so no scan record exists anywhere, and there is nothing to look at. That is a genuine privacy property, and it is also the reason these codes report nothing at all.
A dynamic code encodes a short address on a redirect server, and the phone asks that server where to go before it goes anywhere. The request is the thing that gets counted. Dynamic codes and analytics covers the mechanics, and it is worth understanding that the count exists because of the redirect rather than because of anything clever inside the square.
One more thing gets filed under the same heading by mistake. Finding where your own code lives inside an app, a social profile code or a payment app code, is a different hunt entirely, covered in finding your QR code in the apps you use.
What a scan log can and cannot tell you
Be precise about this, because vendors frequently are not.
Our analytics shows scan counts over time, plus a breakdown by country and by device. That is the list. It answers whether the lobby poster is being scanned, whether scans cluster on weekday mornings, whether the traffic is mostly local, and whether people arrive on phones or on something else.
It does not answer who. There is no identity in a scan, no reliable way to separate a returning visitor from a new one, and no way to connect a scan to a customer record. A spike following a social post and a spike caused by one enthusiastic person with two phones look the same on the chart.
There is also a duty attached to the record. A scan log is a server log, which means it exists before any consent banner on your landing page has had a chance to run, and how long to keep it is a decision somebody has to make on purpose rather than by default. Scan tracking and privacy sets out what those logs contain and where a banner cannot reach.
If you are looking for a code you scanned and have not found it yet, open your browser history and filter to the hour you were standing in front of it. That works more often than anything else in this post.
