A photo is more than its picture. Behind the image sits a set of facts about the file itself: how many pixels wide and tall it is, how many bytes it occupies, what format it is stored in, and when the file was last modified. Those facts, collectively called metadata, answer practical questions that the picture alone cannot. Is this photo high enough resolution to print? Is it too large to email? Is it a recent original or an old recompressed copy? Metadata answers those questions in seconds, without opening an editor.
People usually meet metadata when something goes wrong. A photo prints blurry, a website rejects an upload as too large, or a backup seems to hold a different version of a picture than expected. In each case, the metadata holds the clue: the dimensions explain the blur, the file size explains the rejection, and the modification date explains the version difference. Learning to read those few fields turns vague problems into specific ones.
The iPhone Photo Metadata Viewer tool shows metadata for image files you choose locally. It does not connect to an iPhone, it does not access any account, and it never fetches anything from Apple or any service. It works only on files you choose, in your browser, and it reports what it can read from those files: dimensions, file size, file type, and modification date. Your photos are not uploaded anywhere.
What each field means
Dimensions are the pixel width and height of the image, written as width × height, for example 4032 × 3024 pixels for a typical full-resolution phone photo. That figure decides print size: at 300 pixels per inch, a 4032-pixel-wide photo prints about 13.4 inches wide, because 4032 ÷ 300 = 13.44, while at 150 pixels per inch it prints about 26.9 inches wide. The same photo can therefore be a sharp small print or a soft large one, and the dimensions, not the file size, are what decide that. A photo with small dimensions will never print large and sharp, no matter how large its file size, because file size without pixels is just less efficient storage, not more detail.
File size is the number of bytes the file occupies, and it decides transmission and storage questions: whether the photo fits an email attachment limit, how long it takes to upload, and how much of a storage plan it consumes. Two photos with identical dimensions can have very different file sizes, because compression, detail, and format all affect size. A busy, detailed scene compresses less well than a plain sky, so it produces a larger file at the same dimensions. File size therefore tells you about the cost of the photo, not its quality, and a larger file is not automatically a better photo.
File type, such as JPEG or PNG, tells you how the image is stored. JPEG uses lossy compression, which discards some detail to shrink the file, and it is the usual format for photographs. PNG uses lossless compression, which preserves every pixel, and it is the usual format for graphics with sharp edges and text. HEIC, the format many phones now use by default, compresses photographs efficiently but is less universally supported than JPEG. Knowing the type matters when sharing: a recipient whose software cannot open HEIC will see nothing, while a JPEG will open almost everywhere.
Modification date is the date the file was last changed. It is not necessarily the date the photo was taken. A photo edited, copied, or re-saved gets a new modification date, while its taken date, stored separately inside the file when present, stays with the original moment. If the modification date is much later than the date you remember taking the photo, the file has probably been edited or re-saved since, and the version you hold may differ from the original. Treat modification date as file history, not as photographic history.
A worked example
Choose a sample phone photo and view its metadata. The viewer reports dimensions of 4032 × 3024 pixels, a file size in the low megabytes, a JPEG type, and a modification date. From the dimensions alone you can answer the print question: at 300 pixels per inch, the photo prints about 13.4 inches wide, which suits a standard large print. From the file size you can answer the sharing question: a file of a few megabytes will upload quickly on most connections and fit most attachment limits, while a file of tens of megabytes may not. From the type you can answer the compatibility question: JPEG opens everywhere, so no conversion is needed before sharing.
Now compare that photo with a second file that claims to be the same picture but reports dimensions of 1000 × 750 pixels. The second file is not the original at full resolution; it is a reduced copy, perhaps created for sharing or for a web page. It will look fine on a screen but will print at only about 3.3 inches wide at 300 pixels per inch, because 1000 ÷ 300 = 3.33. That comparison, made from metadata alone, explains why one file prints well and the other does not, without opening either picture in an editor.
A third comparison catches a different problem. Two files report the same dimensions and type, but one is 4 megabytes and the other is 400 kilobytes. The smaller file has been compressed far more aggressively, and it will show compression artefacts, such as blockiness in smooth areas, that the larger file does not. Metadata does not show the artefacts directly, but the size difference at identical dimensions is a strong signal that the two files are not of equal quality.
Common mistakes
The first mistake is confusing file size with quality or resolution. A large file can be a poorly compressed small photo, and a small file can be a well-compressed large photo. Read dimensions for resolution, file size for cost, and type for compatibility, and do not let one field answer another field's question. The second mistake is treating modification date as taken date. They are different facts, and confusing them leads to photos filed under the wrong year and wrong conclusions about when a picture was taken.
The third mistake is assuming metadata is always present. Some applications strip metadata when sharing or exporting, so a photo received from a messaging app may report dimensions and size but no taken date at all. Absence of a field is information too: it tells you the file has passed through a step that removed it. The fourth mistake is sharing metadata carelessly. Photo metadata can include location data, and this viewer focuses on dimensions, size, type, and modification date, but other tools and files may expose more. Before sharing a photo publicly, check what its metadata contains, and remove location data if you do not want it shared.
Honest limitations
This tool shows dimensions, file size, file type, and modification date for image files you choose locally, in your browser. It does not connect to an iPhone, access any account, or fetch anything from Apple or any service. It does not edit metadata, remove location data, convert formats, or recover metadata that has been stripped from a file. It reports what the chosen file contains; it cannot tell you when a photo was taken if that information is absent, and it cannot judge image quality, which requires looking at the picture itself. Very large files take longer to read, and files in unusual formats may report only partial information.
Closing
Read dimensions for print, file size for sharing, type for compatibility, and modification date for file history, and keep those four questions separate. That habit answers most photo problems before they become mysteries. For related work, plan a date-based library with the iCloud Photo Date Organizer tool, strip metadata you do not want shared with the EXIF Privacy Remover tool, and read our guide How to Optimize Images for Websites to prepare photos for publishing.