이미지 메타데이터 뷰어

What metadata is hiding in your image files

Every photo carries two layers of information: the visible pixels, and a block of invisible metadata describing how, when, and where the image was made. This tool surfaces both. The moment you drop in a file it reports the basics any image has — file name, size, MIME type, last-modified date, and pixel dimensions — read directly from the file and the decoded image. For JPEGs it goes further and parses the EXIF block, the standardised metadata that cameras and phones embed at capture time.

EXIF (Exchangeable Image File Format) data can include the camera make and model, the exact date and time of the shot, exposure settings, and — most sensitively — GPS coordinates. This viewer extracts a focused, high-value set of those tags rather than dumping hundreds of obscure fields.

The EXIF fields this tool reads

A worked example

Drop in a JPEG straight from a phone. The tool reads the file as raw bytes, confirms the JPEG start marker, walks the segments until it finds the APP1 segment carrying the Exif header, decodes the TIFF structure inside it (handling both little-endian and big-endian byte orders), and steps through the image file directory to pull each tag. A raw shutter value stored as the fraction 0.004 is converted and shown as 1/250s; an aperture stored as a rational becomes f/1.8. If GPS tags are present, the latitude and longitude — stored as degrees, minutes, and seconds with a N/S/E/W reference — are converted to decimal coordinates like 37.566500° N, 126.977900° E and turned into a clickable Open in Google Maps link so you can see exactly where the shot was taken.

Why this matters for privacy

Geotagged photos are a quiet privacy risk. A picture posted publicly can reveal a home address, a child's school, or a daily route, because the GPS tags travel inside the file. Use this viewer to audit images before you share them: if you see coordinates, strip the metadata (most phones and photo apps offer a "remove location" option on export) before posting. The same applies to the date and camera fields when you would rather not disclose when or with what device a photo was taken.

Practical use cases

• Photographers checking their exposure triangle — shutter, aperture, ISO — across a set of shots to learn what settings produced a result.
• Journalists and researchers verifying when and where an image was captured as a first-pass authenticity check.
• Privacy-conscious users confirming a photo has been scrubbed of location data before uploading it.
• Developers and designers quickly reading pixel dimensions and file size without opening a full editor.

Common points of confusion

• "No EXIF data found." This is normal. Screenshots, images exported from editing software, and pictures already stripped by a social platform usually have no EXIF block at all — the absence is itself useful information.
• PNG, GIF, and WebP show no EXIF. The EXIF standard lives in JPEG (and TIFF). For other formats this tool reports file info and dimensions but states plainly that there is no EXIF block to read.
• Missing GPS even on a JPEG. Many devices have location tagging turned off by default, so a perfectly valid camera JPEG may carry exposure data but no coordinates.
• Timestamps reflect the device clock. The Date/Time field is whatever the camera believed the time was; a wrong device clock yields a wrong EXIF date.

Everything stays on your device

This is a critical point for a tool that exposes location data: the image is never uploaded. It is read with the browser's FileReader and parsed in JavaScript on your own machine. The only network action is optional and entirely under your control — the Google Maps link, which you can choose not to click. You can verify this by disconnecting from the internet: the viewer still extracts and displays everything, because there is nothing being sent.