FILE PRIVACY GUIDE

Run a practical photo privacy check before sharing

A useful photo privacy check combines metadata inspection with a visual review. File Privacy handles supported hidden JPEG and PNG metadata locally; you still decide whether the visible image and sharing context reveal too much.

Open the private checker →

Why this information can matter

Privacy-relevant metadata can include exact GPS coordinates, capture times, camera or lens details, software names, author or copyright text, device serial-related fields, maker notes, publishing containers and comments. These fields vary widely. A simple family photo, screenshot, edited graphic and newsroom JPEG can carry very different information.

A careful browser-local workflow

  1. 1

    Use the final file and check supported metadata before uploading or attaching it anywhere.

  2. 2

    Treat location and identity findings as context-sensitive rather than assuming every metadata item is dangerous.

  3. 3

    Create and re-scan a cleaned copy when supported sensitive containers are unnecessary.

  4. 4

    Review visible faces, badges, screens, documents, addresses and reflections, then consider the audience and permanence of the destination.

What this version supports

The tool accepts JPEG/JPG and PNG up to 50 MiB. It groups supported findings into location, identity, device, time, software and metadata categories. For supported files it can remove implemented JPEG EXIF/XMP, IPTC/Photoshop and comment containers or PNG EXIF, text and time chunks, then scan the created copy again.

Limits to keep in mind

This workflow is not an anonymity guarantee, legal review or forensic certification. Unsupported metadata may remain, and the checker cannot recognize sensitive visual content or predict how a third-party service processes a file. Keep the original separate, review the clean-copy verification, and make a sharing decision appropriate to the people and information involved.

Inspection and cleanup run in your browser. Selected file bytes are not uploaded to FrAIFlow servers. The result describes only the supported structures this release can observe.

Related File Privacy guides

Check the file you plan to share

Use the real File Privacy checker for a supported JPEG/JPG or PNG file up to 50 MiB.

Check metadata locally →Browse all guides

Before downloading and sharing

The input limit is 50 MiB (50 × 1024 × 1024 bytes), and browser decode validation allows up to 24,000,000 pixels. For example, 6000 × 4000 fits that pixel limit; 6000 × 4001 does not, even if the file is below 50 MiB.

The new copy must pass the same supported metadata parser, structural checks and browser decoding, with no remaining supported findings. Validation also checks GPS status and preserved orientation. A JPEG may retain minimal orientation-only EXIF to preserve how it is displayed. Image data is not recompressed. These implemented checks do not certify complete erasure, anonymity or safety.

If processing fails, the result is unknown and no verified clean-copy download is offered. Check the format, size and file condition before retrying. Use a trusted, updated browser. Before sharing, review the filename and visible image for private information, and consider the recipient and destination.