Processed locally
Your input stays in this browser.
On most current phones, the built-in Camera app itself is the QR code scanner: no separate download is needed, since Android 9 and later and recent iOS versions recognize a QR code automatically when the camera is pointed at it. A separate scanning app is only necessary for older devices, batch scanning, or reading a saved image file rather than a live camera feed.
The built-in camera is usually the scanner already
Most people searching for a QR code scanner already have one installed: the default Camera app on a current Android phone or iPhone recognizes a QR code automatically when it is in frame, without opening a separate application first. Google documents this directly for Pixel phones, noting that the Camera app can scan a QR code as long as the device runs Android 9 or higher and a setting called Camera scan suggestions is turned on, after which the camera shows a link or action bubble on screen the moment it recognizes a code rather than requiring a photo to be taken. If a phone's camera is not offering that suggestion, the first thing to check is that specific setting, not a separate downloaded app.
When you actually need a separate scanning app
A dedicated scanning app earns its place in a few specific situations the built-in camera does not cover well: an older phone running a version of Android below the one Google's own documentation specifies as the minimum for built-in recognition, a workflow that needs to scan many codes in quick succession and log the results rather than open each one individually, or a need to read a QR code from an already-saved image file — a screenshot, a downloaded PDF, or a photo taken earlier — rather than from a live camera pointed at a physical object. None of these are reasons the built-in scanner is broken; they are reasons its live-camera, one-at-a-time design does not match the specific task.
| Situation | Best tool | Why |
|---|---|---|
| Everyday live scan on a current phone | built-in Camera app | no install needed, works automatically |
| Reading a saved screenshot or photo | upload-based reader | no live focus or hand-shake involved |
| Checking many saved images at once | batch reader | avoids opening each file individually |
Worked example: a code that will not scan with the camera but decodes fine from a saved photo
A QR code printed at a small size on a glossy, curved product label can be genuinely difficult for a phone's live camera to lock onto, because autofocus has to settle at close range on a reflective, non-flat surface at the same time the frame is being held steady by hand. Photograph the same label carefully, at an angle and distance that avoids the glare, and an upload-based reader working from that saved image file can succeed where the live-camera attempt kept failing, because it only has to process one already-captured, already-focused frame rather than continuously refocus a moving preview. This is not a contradiction: it reflects a genuine difference between decoding a live, changing camera feed and decoding a single still image someone already confirmed looks clear.
What a QR scanner is actually checking when it fails
A QR scanner failing to recognize a code is almost always a locating or contrast problem, not a data problem: the scanner has to first find the three distinctive corner squares that mark a QR code's position and orientation, and anything that obscures, crops, or distorts those corner patterns — a logo placed over one corner, a code cropped too close to its edge, or a code printed at an angle to the camera — can prevent recognition even though the underlying data would decode correctly once located. Low contrast between the modules and the background, whether from poor print quality or a coloured background chosen for design reasons, has the same effect: the scanner cannot reliably tell a dark module from a light one, so it never gets far enough to attempt the actual decode.
Reading a saved image instead of a live camera feed
Reading a QR code from a saved image file, rather than a live camera, is a fundamentally different and often easier task, because the image is already captured, focused, and stable — there is no autofocus hunting, no hand shake, and no need to hold a phone steady while a preview updates in real time. A file-upload-based reader accepts a PNG, JPEG, or WebP image directly, decodes it once against that fixed frame, and reports the result, which is well suited to checking an already-exported QR file before printing, verifying a screenshot someone sent you, or decoding a code from a photo taken under conditions where a live scan struggled. It is not, however, a substitute for a live camera scanner when the actual task is pointing a phone at a physical object in the moment.
Common QR scanning mistakes that look like a broken code
A frequent cause of an apparently failed scan is holding the phone too close for the camera to focus, especially on a small printed code, rather than any fault in the code itself; backing away slightly and letting autofocus settle usually resolves it. Another is scanning under strong overhead or direct light that creates glare directly over the code's surface, which behaves like a contrast problem even though the print itself may be perfectly fine — tilting the phone or the printed material slightly to move the glare off the code often fixes this without any change to the artwork. A third is assuming a scan failure means the encoded data is wrong, when the far more common cause, especially for a code that scanned successfully before, is a physical change to the printed copy: a fold, a smudge, or fading that a fresh export would not have.
What scanning successfully does not tell you
A successful scan confirms that the camera or reader correctly measured the pattern of modules and reconstructed the encoded data; it does not confirm that the destination the code points to is safe, current, or the one the person who printed the code actually intended. A decoded web address can still lead to an expired page, a changed destination, or a deliberately misleading link, and none of that would show up as a scanning failure — the code would scan perfectly while still leading somewhere unhelpful or unsafe. Treat a successful scan as the first step of evaluating a QR code, not the last one, especially for a code encountered somewhere unexpected rather than generated by a source you already trust.
Turning automatic recognition off when you do not want it
Automatic QR recognition in a phone's Camera app is convenient for a code you intend to scan, but the same always-on recognition can pop up an unwanted link suggestion every time an unrelated pattern in a photo or the background happens to resemble a code, which some people find distracting enough to want disabled. Google's Pixel documentation frames the recognition behaviour as controlled by the same Camera scan suggestions setting used to enable it, meaning the feature can be turned off for someone who prefers to open a scanning tool deliberately rather than have the camera offer a suggestion automatically. Knowing that this is one toggle, not a hidden system behaviour, matters for troubleshooting in both directions: a scanner that seems too eager and one that seems to have stopped working are frequently traced back to the same single setting. The same principle applies beyond Pixel devices: most current phones expose an equivalent toggle somewhere in their camera or system settings, even where the exact menu wording and location differ between manufacturers and software versions, because the underlying trade-off — convenience from automatic recognition versus fewer unsolicited suggestions — is the same regardless of who built the phone. When troubleshooting a QR scanning complaint on an unfamiliar device, checking whether automatic recognition is enabled at all is a faster first step than assuming a hardware or camera fault, since a disabled recognition setting produces exactly the same symptom — nothing happens when a code is in frame — as a genuinely broken camera would. Google: Scan QR codes with your Pixel phone is the named source for the current external rule or product behaviour.