10/12/2026
How to Tell If a Photo Was Taken on iPhone or Android
Every digital photo carries a hidden technical record inside it, and that record often answers the question of which phone took it with surprising precision. When you press the shutter button on an iPhone or an Android device, the camera software writes dozens of metadata fields into the image file โ the make and model of the device, the exact lens used, exposure settings, timestamps, and sometimes GPS coordinates. This data, mostly stored in a standard called EXIF (Exchangeable Image File Format), is embedded directly into the file and travels with it when you copy, email, or archive the photo โ at least until something strips it out. Learning to read this metadata is useful far beyond curiosity: journalists verifying a source's claims, lawyers assessing photographic evidence, and investigators tracing the origin of a leaked image all rely on exactly these fields. The good news is you don't need to be a forensic examiner to do it.
The fastest way to start is with the metadata fields labeled "Make" and "Model." On an iPhone photo, the Make field almost always reads "Apple," and the Model field contains something like "iPhone 14 Pro" or "iPhone 15." Android photos show far more variety: a Samsung might record "samsung" as the Make with a model string like "SM-G991B" (a Galaxy S21), while a Google Pixel shows "Google" and "Pixel 7 Pro." Xiaomi, OnePlus, Motorola, and other manufacturers each leave their own fingerprints. If you see "Apple" in the Make field, the photo came from an iPhone โ or at least passed through one. If you see a model number you don't recognize, a quick web search of that string will identify the handset. This single check resolves the iPhone-versus-Android question in the majority of cases, because most people share photos without deliberately editing metadata.
Beyond Make and Model, several subtler signals reinforce the conclusion. iPhones running recent iOS versions often shoot in HEIC format by default, so a .heic file is itself a strong hint of an Apple device, though iPhones can also produce JPGs and Android 10+ devices can optionally shoot HEIC too. The Software field is another giveaway: iPhone photos typically carry an iOS version string like "17.4.1," whereas Samsung photos often reference the camera firmware, and photos processed by Adobe Lightroom mobile will say so regardless of platform. Lens metadata differs as well โ Apple writes descriptive lens strings such as "iPhone 14 Pro back triple camera 6.86mm f/1.78," while Android manufacturers use their own conventions. Even the filename offers a soft clue: iPhones name files "IMG_0001.HEIC," Pixels use "PXL_20240115_123456789.jpg," and Samsung uses timestamp-based names like "20240115_143022.jpg." Filename alone proves nothing โ files get renamed constantly โ but combined with EXIF data it adds confidence.
So how do you actually see all this? On any computer, you can right-click an image and inspect its properties, but built-in viewers show only a fraction of what's there. For a complete picture, upload the photo to FilesAudit and the platform will extract the full metadata block โ EXIF, XMP, and IPTC fields alike โ including device make and model, lens details, GPS coordinates if present, timestamps, and editing software traces. It also computes cryptographic hashes (SHA-256, MD5, CRC32) of the file, which matters if you later need to prove the image you examined is the same one entered into evidence or a report. If you're specifically working with JPEGs, the dedicated JPG metadata guide walks through which fields to expect and what each one means in practice.
Here's a practical example. A freelance journalist receives a photo from a source claiming it was taken "on my Samsung" at a protest last weekend. She uploads it and finds Make: Apple, Model: iPhone 13, Software: Instagram. Two things become clear immediately: the photo was captured on an iPhone, not a Samsung, and it was passed through Instagram โ which explains why the GPS data is gone (social platforms strip location metadata on export). The source may simply have misremembered, or the photo may have come from someone else's phone entirely. Either way, the metadata reframed the story. Notice what the analysis did *not* do: it didn't prove who took the photo or whether the scene was staged. Metadata tells you about the file's history, not the truth of its contents โ an important distinction in any investigative or legal context.
That caveat deserves emphasis, because metadata can be missing, stripped, or deliberately forged. Messaging apps like WhatsApp and Messenger compress images and remove most EXIF data; screenshots contain no camera metadata at all, just device screen dimensions; and freely available tools let anyone rewrite the Make and Model fields in seconds. Absence of metadata doesn't prove manipulation โ it's often just the expected result of normal sharing. Conversely, pristine metadata isn't proof of authenticity either. What metadata gives you is evidence to weigh, not a verdict. For higher-stakes work, pairing metadata analysis with cryptographic hashing is the professional approach: the hash documents the exact file you examined, so any later copy can be compared bit-for-bit. If you're building that kind of workflow, it's worth reading about how to check if two files are exactly identical, since hash comparison is the backbone of file integrity verification.
There's also a newer layer worth knowing about: C2PA content credentials. Some recent devices and camera apps โ including Google's Pixel line in certain modes โ now cryptographically sign provenance data at capture time, recording the device and any subsequent edits in a tamper-evident way. Unlike ordinary EXIF, which anyone can edit, C2PA credentials are designed to break visibly if altered. FilesAudit extracts this AI-generation and provenance evidence alongside traditional metadata, so you can see whether a photo carries signed capture credentials or shows signs of AI generation. Adoption is still early, so most photos you'll encounter won't have it โ but when it's present, it's a far stronger signal than EXIF alone.
For one-off checks, the browser-based workflow is enough: upload, review the extracted fields, download the PDF report if you need documentation. But professionals handling hundreds of images โ say, a legal team sorting a photo production by device type, or an archivist cataloging a donated collection โ will want bulk processing without uploading sensitive files anywhere. That's what the FilesAudit Desktop App is built for: unlimited local metadata extraction and hashing across 200+ supported formats, from HEIC and RAW images to video, audio, and documents, all processed on your own machine. Whether you're answering a quick question about one suspicious photo or auditing an entire evidence folder, the underlying principle stays the same: devices leave fingerprints in their files, and knowing how to read them turns a simple image into a documented piece of technical evidence.