What this workspace does
A metadata-only density update, plus an honest pixel-versus-print-size explanation.
Image Inspector · browser local
Set image density to 300 PPI locally without changing pixels. Use the resizer when you need more pixels instead of a metadata-only print-layout update.

A metadata-only density update, plus an honest pixel-versus-print-size explanation.
Changing 72 to 300 PPI does not create detail. It changes the suggested physical size at which the existing pixels are placed.
Selected files are processed in the current browser session. Aftermath has no account, cloud file storage, or server-side file-processing job.
Set print-density metadata on a separate local image copy when a destination asks for 300 DPI/PPI but the pixel canvas itself is already appropriate. The operation changes supported metadata and verifies the output without inventing extra pixels or image detail. Check the destination's actual pixel and format requirements as well as its density wording.
A 1200-pixel-wide image needs a copy labelled 300 PPI for a print workflow while retaining the same pixel grid.
Observed operation: Write a separate image copy with 300 PPI density metadata and keep the decoded width and height unchanged.
Review the result: Reopen the copy, confirm its pixels match the source and verify the new density and calculated physical size.
Boundary: Changing a density label cannot create pixels, improve sharpness or force another application to honor that print size.
The selected image stays in the current browser session and is not sent to an Aftermath processing service. How local processing is verified.
Checks the displayed limits and reports or creates a separately downloaded image copy with changed print-density metadata and unchanged pixels from one supported local image.
A local measurement or export does not guarantee acceptance by an external destination.