filesaudit.com

10/12/2026

How to Find Out What Camera or Phone Took a Photo

Almost every digital photo carries a hidden identity card. When a camera or smartphone captures an image, it embeds a block of data called EXIF (Exchangeable Image File Format) into the file itself, and that data typically includes the camera manufacturer and model, the lens used, exposure settings like aperture and shutter speed, the exact date and time of capture, and sometimes even GPS coordinates. If you've received a photo and want to know what device created it — whether you're verifying a source's claims, organizing an archive, investigating a copyright dispute, or just curious — EXIF is almost always the first place to look.

The catch is that this metadata isn't visible when you simply open the image. You need a tool that reads the embedded fields. The good news: you probably already have several options on your computer, and there are more powerful options when the built-in ones fall short.

On Windows, the quickest method is to right-click the photo, choose Properties, and open the Details tab. Scroll down and you'll often see entries like "Camera maker" (Canon, Nikon, Sony, Apple, Samsung) and "Camera model" (EOS R5, iPhone 15 Pro, Galaxy S24). On a Mac, open the image in Preview, press Command-I, and click the "i" tab, then the EXIF sub-tab — macOS presents a clean breakdown including lens model and ISO. On an iPhone itself, open the photo in the Photos app and swipe up; Apple shows the device model, capture date, and even a map if location data exists. Android's Google Photos does something similar when you tap the three-dot info menu. These built-in viewers are fine for a quick answer to "what camera took this," but they only show a curated subset of the metadata and they have no way of telling you whether that metadata looks consistent or tampered with.

For a deeper look, dedicated metadata readers come into play. ExifTool, a free command-line program by Phil Harvey, is the forensic community's workhorse: running `exiftool photo.jpg` dumps every embedded tag, including maker notes (manufacturer-specific fields that can contain the camera's serial number, firmware version, shutter count, and internal processing settings). If you'd rather not touch a terminal, browser-based tools can do the job without installing anything. Uploading a photo to FilesAudit, for example, extracts the full EXIF, XMP, and IPTC metadata along with a SHA-256 fingerprint of the file, and packages everything into a professional PDF report — useful when the answer to "what camera took this" needs to be documented rather than just glanced at, as in an insurance claim or a legal dispute.

Now, a practical example of what you'd actually see. Take a JPEG straight off a Canon camera: the Make field reads "Canon," Model reads "Canon EOS 90D," and the maker notes may include a body serial number and a shutter actuation count. A photo from an iPhone 15 Pro shows Make "Apple," Model "iPhone 15 Pro," plus a LensSpecification describing which of the three physical cameras was used and computational flags indicating Deep Fusion or Night mode was active. An Android shot from a Pixel shows Make "Google" with model strings that often include a build number. These differences are consistent enough that experienced investigators can often identify the device class even from partial data. If you want a focused walkthrough of the smartphone side of this, the guide on how to tell if a photo was taken on an iPhone or Android goes field by field.

Here's where things get interesting — and where naive reading of EXIF can mislead you. First, metadata is routinely stripped. Facebook, Instagram, Twitter/X, WhatsApp, and most messaging apps remove EXIF data when you upload or send an image, both to save bandwidth and to protect user privacy. So if the photo you're examining came from social media, an empty metadata block doesn't mean the camera data never existed; it means a platform deleted it. The original file on the photographer's phone still has everything. Second, metadata can be edited. ExifTool and dozens of other utilities can rewrite the Make and Model fields in seconds, so EXIF alone is evidence, not proof. A camera model string is what the file *claims*; confirming that claim requires looking at internal consistency — do the lens fields match lenses that actually exist for that body? Does the maker-note structure match the manufacturer's known format? Does the image dimensions and thumbnail match what that camera produces?

This consistency analysis is where forensic-grade tooling earns its keep. FilesAudit, for instance, doesn't just list fields — it documents the complete metadata set alongside cryptographic hashes, so an analyst can compare a suspect file's metadata structure against a known-genuine reference file from the same camera model and compute whether the two files are byte-identical or merely similar. That's a meaningful distinction in disputes over photo authenticity: the platform documents the technical evidence rigorously, while the legal conclusion about authenticity still belongs to the expert or the court. For format-specific quirks — JPEGs carry the richest EXIF, while PNGs store metadata differently through XMP chunks and text blocks — the dedicated JPG metadata guide and PNG metadata guide explain what each format can and cannot contain.

A few edge cases are worth knowing before you draw conclusions. Screenshots have no camera metadata at all — they typically show the operating system or screenshot software in the Software tag instead, which is itself a clue that the image was captured from a screen rather than a lens. Photos saved from editing apps like Lightroom or Photoshop usually retain the original Make and Model but gain a Software field and a ModifyDate that postdates the original DateTimeOriginal — a telltale sign of post-processing. RAW files (CR3, NEF, ARW, DNG) carry even richer maker notes than JPEGs, often including focus distance and autofocus point data. And images generated by AI may carry C2PA provenance credentials — a cryptographically signed content record — or conversely, suspiciously clean metadata that no real camera produces. FilesAudit supports over 200 formats including RAW and can surface C2PA provenance evidence when it's present, which increasingly matters as synthetic imagery floods journalism and legal workflows.

So the practical workflow looks like this. Start with the built-in viewer on your device for a fast answer. If the Make and Model fields are present, note them but treat them as claims. If the metadata is missing or the stakes are high, pull the full tag set with ExifTool or a forensic platform, check internal consistency across fields, compare against a reference image from the claimed camera if you have one, and hash the file so you can prove later exactly which bytes you examined. That combination — full metadata extraction, consistency review, and a documented hash — is the difference between casually guessing what camera took a photo and actually being able to defend your answer.

Ready to see what's hidden in your own files? Upload a file to FilesAudit and get a free forensic metadata report in seconds — no registration required.