Image DPI Changer updates print-density metadata in one JPEG or PNG at a time, so changing DPI for multiple images means repeating the same local workflow for each file rather than using a batch selector. The tool accepts one JPEG or PNG no larger than 25 MiB, and no file is uploaded to a server. For each image, choose the file, review any detected density, enter a whole-number target, select Update image DPI, and download the new copy. The source pixels and compressed image data are copied as bytes, so pixel dimensions do not change and the process does not crop, sharpen, enlarge, compress, or create a second lossy JPEG encoding. Because each file is handled separately, keep the original, use a clear naming pattern for the downloads, and verify every result in the layout or print application that will use it. This operation changes a physical-size instruction; it does not manufacture detail or reliably change how a website lays out an image. It also does not convert an unsupported format into JPEG or PNG.
What bulk DPI changing means here
Search wording such as “change image dpi bulk multiple images” often implies a multi-file drop zone. Image DPI Changer does not provide that: its documented unit of work is one file. A collection is therefore completed by processing and downloading each item separately. The 25 MiB ceiling applies to every selected file, not to a combined collection. JPEG and PNG are the only accepted inputs, so a file in another format must be converted before it can be changed here. If one target applies to the whole set, enter it on every run. If print requirements differ, keep a record that links each original name, target DPI, and downloaded filename.
This makes the tool a repeatable batch workflow, not a one-click batch uploader. It suits collections where each result needs individual inspection. The operation stays focused on density metadata: it does not add margins, estimate printer quality, convert formats, or alter the image canvas. Those limitations matter because a print provider may require more than a DPI label.
Update each image in a repeatable batch
Use the following sequence for every JPEG or PNG in the collection:
- Set the collection rule. Record the intended physical size and the whole-number DPI required by the destination. If a print provider supplies its own pixel, profile, bleed, or format requirements, keep those requirements alongside the DPI target.
- Select one image. Choose a JPEG or PNG file no larger than 25 MiB. The 25 MiB limit applies separately to each file you process.
- Review the detected information. Check any usable JFIF or PNG pHYs density reported after selection. The page also reads standard EXIF resolution fields, but a displayed value does not guarantee that every destination application will prefer it.
- Enter the target DPI. Use a whole number for the print-density instruction you want the output copy to carry. Do not enter a physical dimension or a percentage in this field.
- Select Update image DPI. The tool updates the documented density field for the selected format while retaining the source pixel dimensions and compressed image data.
- Download the updated copy. Give the file a name that connects it to its original and target DPI, then move to the next image. Repeat the selection, target entry, update, and download actions individually.
- Verify the intended size. Place each downloaded copy at its planned physical size in the destination layout or print application. Confirm the complete image fits as expected before using it in the final deliverable.
Keep the untouched originals and compare each result with its source before delivery. A matching pixel count confirms that DPI metadata changed, but only the destination workflow can confirm how it will use that metadata.
Derive the target from print dimensions
DPI is a print-density instruction, not a quality score. Start with the physical size you need and the pixels already available in the source. If the print dimensions have not yet been worked out, the DPI Converter can help establish the relationship before you change a file.
Available pixels ÷ intended inches = required pixels per inch
For example, a 3600-pixel-wide image intended to print 12 inches wide gives 3600 ÷ 12 = 300 pixels per inch. Enter 300 as the target, then place the downloaded copy at 12 inches wide and inspect the complete design at its final output size. Confirm that the height and composition also fit the intended layout.
The calculation assigns an intended print size to pixels that already exist. It does not supply more detail. Inspect small text, edges, and photographic areas at final dimensions; metadata cannot compensate for an undersized source. If the actual pixel count must change, use the Image Resizer instead. If the source does not contain enough visual information for the planned print size, obtain a higher-resolution source rather than expecting a DPI label to repair it.
What changes at each DPI value
The table below separates the physical-size instruction from the underlying image data:
| Metadata action | Pixel dimensions | Intended print size | Image detail |
|---|---|---|---|
| Raise the DPI value | Stay unchanged | Becomes smaller at the same pixel count | No pixels or detail are added |
| Lower the DPI value | Stay unchanged | Becomes larger at the same pixel count | No pixels are deleted |
DPI tells a printer or layout application how many existing image pixels should be placed within each physical inch. Raising the value can make an image occupy less space on a printed page, but it cannot improve a blurry photograph or turn a low-resolution scan into a high-resolution source. Lowering the value produces the opposite size relationship without removing content.
The compressed image data is copied rather than decoded and encoded again, so the tool avoids a second lossy JPEG encoding. The density field and total file size can still change because metadata bytes are being updated; this is not a promise that every byte or every metadata family in the complete file remains identical. A normal website generally displays an image according to its CSS or layout dimensions, so a higher DPI label does not make the on-screen image sharper.
JPEG and PNG store the instruction differently
The output format determines which documented metadata field receives the new density value:
| Format | Field updated | Stored unit | Important behavior |
|---|---|---|---|
| JPEG | JFIF APP0 density fields | Dots per inch | If no JFIF density header exists, the output adds a small JFIF header |
| PNG | pHYs physical-pixel chunk | Integer pixels per metre | A readback can differ from the requested DPI by a tiny rounding fraction |
For JPEG, the tool reads or writes the JFIF APP0 density fields using the standard dots-per-inch unit. The W3C JPEG File Interchange Format 1.02 specification defines this file structure and its density fields.
For PNG, the tool writes the standard pHYs chunk using pixels per metre. It performs the conversion with the exact 0.0254-metre-per-inch relation, but PNG storage requires an integer pixels-per-metre value. That limitation can cause a very small rounding difference when the file is read back. The W3C PNG specification defines the chunk. This rounding changes neither the PNG's pixel dimensions nor its image detail.
Prevent metadata conflicts and stale results
After a file is selected, the page reports whether it found usable JFIF or pHYs density and dynamically reads standard EXIF resolution fields. It does not attempt to merge or rewrite every possible EXIF, XMP, ICC, IPTC, camera, GPS, or vendor extension. A JPEG can contain several forms of resolution information, and different applications may choose different fields. The generated JFIF or pHYs value is therefore useful documented metadata, but it cannot force every program to display the same physical size.
The page validates the file signature and bounded header structure before creating updated metadata. It rejects truncated JPEG marker segments, malformed PNG chunks, duplicate physical-pixel chunks, or a pHYs chunk placed after image data rather than attempting an optimistic repair. If an operation fails, the page clears its old result link instead of presenting a previous download as though it had just been updated. Download each successful result promptly and confirm its filename before starting the next file.
Check the finished multiple-image set
Before delivering or printing the collection, run this final check:
- Keep every untouched original in a separate folder or archive.
- Pair each downloaded file with its original name and intended DPI.
- Confirm that each source was a JPEG or PNG no larger than 25 MiB.
- Check that pixel dimensions remain the same; do not expect a metadata change to add detail.
- Open each result in the destination application and place it at the intended physical size.
- Inspect text, edges, and photographs at the final output dimensions.
A print provider may specify a minimum pixel count, export profile, bleed setting, or file format in addition to DPI. Follow the provider's documented requirements rather than assuming that a DPI label alone satisfies the job. Keep the original, test the downloaded copy in the application or printer workflow that matters, and retain the verified version for delivery.