Check image software history for a press kit

Before a photo goes into a company press kit, you may want to know which software saved or edited it. That information can be useful, but a metadata field is only a clue, not a complete record of every change.

Use the Photo Info & Cleaner to inspect image details, check for software-related metadata, and remove private information from a separate copy if needed. Keep the original file unchanged so you can compare versions and preserve your source material.

Check an image's software history

1. Open the Photo Info & Cleaner and choose a copy of the image you plan to use. The image stays on your device while you inspect it in the browser.
2. Review the available metadata for software-related entries. Look for fields such as Software, Creator Tool, or an XMP history entry. The names and availability depend on the file and its metadata.
3. Note the exact value and any date or application name shown. Do not assume that a familiar editor name proves who made the image or what edits were performed.
4. Compare the information with your production records, such as the original camera file, approved export, or designer's project file. Check that the image is the approved version before putting it in the kit.
5. If you need to remove personal details, work from a duplicate and use the tool's metadata-cleaning function. Inspect the cleaned copy afterward to confirm the details you wanted removed are gone.

If the tool shows no software information, you can make a quick secondary check in your operating system. In Windows 11, right-click the image in File Explorer, choose Properties, then open Details. On macOS, select the file in Finder and choose File › Get Info. These views may show only a portion of the embedded metadata, so use the browser tool for a fuller inspection.

What the metadata means

A software or creator-tool name appears

This usually means that the named application wrote or updated a metadata field when it saved or exported the file. It can help you recognize a workflow or spot a file that differs from your expected export. It does not prove that the application created the picture from scratch, or that the named software performed every edit.

An XMP history entry appears

XMP is a metadata format that can store extra information, including history-style entries. An entry may identify a tool or an action, but not every app writes this data, and some exports remove it. Treat it as supporting context rather than a certified edit log.

No software history appears

The file may never have included that information, or it may have been removed during export, resizing, messaging, or upload. A blank field does not mean the image was never edited. If the press kit needs a verified source, ask the photographer or designer for the approved original or project records.

The software name looks unexpected

It could reflect an ordinary step, such as resizing or converting the image in another program. It could also be a metadata value carried over from an earlier file. Check the approved image and production records before treating the name as a problem. Metadata can be copied or changed, so it cannot establish the full history on its own.

Prepare a clean press-kit copy

1. Keep the original. Save an untouched source file in your approved asset folder. Make a separate copy for cleanup or distribution so you can return to the original if you need to verify a field.
2. Confirm the source and approval. Compare the candidate image with the photographer's delivery, the design team's approved export, or your asset records. Do not use metadata alone to establish ownership, permission, or approval.
3. Remove only what you need to remove. Use Photo Info & Cleaner on the duplicate if you want to strip metadata before sharing. Location coordinates, device details, and personal names may be sensitive. Check attribution and licensing requirements separately before removing credits or creator information.
4. Inspect the cleaned copy again. Reopen it in the tool and check the fields you intended to remove. Also open the image itself to confirm it still looks right and has the expected dimensions and format.
5. Keep useful records outside the image. Store the credit line, license, approval status, source filename, and any relevant editing notes in your press-kit records. A metadata cleaner may remove information that your team needs later.

Do not overwrite a source image simply to make its software field look different. If the field conflicts with your records, preserve the file and ask the person who supplied it to confirm the workflow. A changed metadata value is not the same as a verified edit history.

What metadata can and cannot prove

Image metadata is information stored alongside the visible picture. Some fields describe the camera or date, while others may be written by editing or export software. Different formats and applications preserve different fields, and many publishing systems remove some metadata automatically.

That makes metadata useful for a quick review, not a forensic guarantee. A software label can be edited, copied from another file, or left behind after a new export. It rarely documents every operation in order. For a press kit, use it to flag questions and then verify the image against trusted source files and approval records.

Files opened in TooLab tools stay on your device. Keep a separate, approved copy for any metadata cleanup before sharing it with colleagues or the public.