NoLogPDF
NoLogPDF
Local browser workspace
NoLogPDF

Fast, free, browser-only tools. Your files stay on your device.

61 browser tools Works on mobile Free to use

No File Logs

We do not upload, store, or track the files you process.

No Backend

All processing happens inside your browser.

100% Free

Every tool is free. No hidden costs.

Total Transparency

Built for trust with clear local limits.

Utility Tools / Stable

View Image Metadata Online

Inspect an image's browser-detected format, pixel dimensions, and file size without changing it.

Quick answer

What does Image Metadata do?

Inspect an image's browser-detected format, pixel dimensions, and file size without changing it. The selected image is processed locally in this browser without being sent to a backend conversion server. The report focuses on basic browser-readable properties rather than every EXIF or proprietary field.

Use Image Metadata when you need to inspect local image dimensions, format, and size. Common uses include verify image dimensions before upload, check actual file format and size, compare assets during website preparation.

Input
image
Processing
In this browser
File upload
No
Price
Free

Designed around the task

Why use Image Metadata?

Focused controls, local processing, and clear limits help you finish the job without sending the document to a conversion server.

Focused results

Reads file properties and decoded image dimensions for display.

Useful browser controls

Does not rewrite the image or alter its metadata.

Desktop and mobile

Use Image Metadata in a current desktop or mobile browser without installing a separate app.

Simple local workflow

Create an output you can inspect before sharing.

Private by design

The selected image is processed by JavaScript running in this browser for Image Metadata. NoLogPDF does not send it to a backend conversion API, and file names, contents, form values, passwords, and output data are excluded from site analytics.

Automatic file recognition

NoLogPDF checks the selected file in your browser and shows the controls available for Image Metadata.

How to use Image Metadata

  1. Choose an image.
  2. Wait for the browser to decode its dimensions.
  3. Review the displayed format, size, width, and height.
  4. Download the report only if the interface offers one.

What Image Metadata changes

  • Reads file properties and decoded image dimensions for display.
  • Does not rewrite the image or alter its metadata.

Browser-only privacy

The selected image is processed by JavaScript running in this browser for Image Metadata. NoLogPDF does not send it to a backend conversion API, and file names, contents, form values, passwords, and output data are excluded from site analytics.

Limits to know before using Image Metadata

  • The report focuses on basic browser-readable properties rather than every EXIF or proprietary field.
  • Unsupported or damaged image formats may not decode.

Common uses for Image Metadata

  • Verify image dimensions before upload.
  • Check actual file format and size.
  • Compare assets during website preparation.

Image Metadata questions

How does Image Metadata work?

Inspect an image's browser-detected format, pixel dimensions, and file size without changing it. Choose an image. Wait for the browser to decode its dimensions. Review the displayed format, size, width, and height.

Does Image Metadata upload my image?

No. The selected image is read by code running in this browser for this operation. NoLogPDF does not send it to a backend conversion API or include document data in analytics.

What does Image Metadata change in the output?

Reads file properties and decoded image dimensions for display. Does not rewrite the image or alter its metadata.

What limits should I know before using Image Metadata?

The report focuses on basic browser-readable properties rather than every EXIF or proprietary field. Unsupported or damaged image formats may not decode.

Published and maintained by NoLogPDF

How this tool page is checked

The instructions describe this browser implementation, its expected output, and its known limits. Core workflows are exercised with local fixtures, output files are validated where the format allows, and mobile behavior is checked at a narrow viewport.