To change image DPI for an email attachment, update the JPEG or PNG's print-density metadata locally, then download the copy without changing the image's pixel dimensions.
DPI is a print-density instruction: it tells a compatible layout or print workflow how many existing image pixels should occupy one physical inch. It is not a way to create extra pixels, sharpen a photo, or reduce the number of bytes in an attachment. An attachment can be sent without changing its DPI, so edit it only when the recipient's print workflow needs a particular physical size or the destination process explicitly asks for one.
For that focused job, the Image DPI Changer changes the density instruction in a single JPEG or PNG while leaving the actual pixels alone. It runs locally, so the source file does not need to be uploaded to a server. That makes it suitable for preparing a print-oriented attachment, but it does not turn the tool into a file-size reducer.

DPI and the size of an email attachment
An image can have pixel dimensions, print-density metadata, and an encoded file size at the same time. These properties are related, but each one answers a different question.
| Image property | What it controls | What it does not control |
|---|---|---|
| Pixel dimensions | The number of pixels available for display or printing | The DPI instruction used to calculate physical size |
| DPI metadata | How a compatible application maps pixels to physical inches | Detail, sharpness, or attachment byte size |
| Encoded file size | How much data the attachment contains | Pixel dimensions or print density by itself |
If an email recipient simply opens the image on screen, a changed DPI value may have no visible effect because the viewing application can choose its own display size. If the attachment will be placed in a document, sent to a print provider, or opened in a print application, the density metadata can influence the initial physical-size calculation. Even then, the application may use other metadata, and the final layout size should still be set and inspected.
That is why an attachment can need a DPI change without needing a pixel resize. The file may already contain enough pixels for the requested print dimensions, but its density instruction could point to the wrong size. Conversely, a small file can still be unsuitable for print if it does not contain enough pixels. Decide whether the real problem is physical size, detail, or file weight before editing.
Choose a target from the intended print size
Start with the physical size you want, then calculate the DPI that produces it. For the width, use the following relationship:
Target DPI = image width in pixels ÷ intended width in inches.
For example, a 3600-pixel-wide image intended for a 12-inch-wide print needs 3600 ÷ 12 = 300 DPI. The same DPI applies to the height, so the image's pixel aspect ratio should match the intended print shape.
The changer accepts a whole-number target, with common choices such as 72, 150, 300, and 600. A higher number tells a compatible workflow to place the same pixels in a smaller physical area; a lower number tells it to place them in a larger area. Neither operation adds or removes pixels. If you need to work out the physical size before editing, the DPI Converter can translate pixel dimensions and an intended DPI into print-size calculations.
When a print provider specifies a pixel count, export profile, bleed, or file format, follow that provider's documented requirements instead of relying on a DPI number alone. DPI is one part of the output, not a complete production specification.
Change image DPI for an email attachment
- Confirm the source file. Make sure you have one JPEG or PNG image no larger than 25 MiB. The changer does not accept batches or other formats, and it does not convert formats for you.
- Decide the intended print dimensions. Establish the target width and height before choosing a DPI value. If the attachment is only an on-screen preview and no downstream workflow requests print density, changing DPI may not be necessary.
- Select the image and review its metadata. Open the Image DPI Changer, choose the JPEG or PNG, and review the detected print-density information. The page reports whether it found usable JFIF or pHYs density metadata.
- Enter the whole-number target DPI. Use the value calculated from the intended physical size rather than automatically choosing the highest available number.
- Run the local update. Select Update image DPI. For a JPEG, the tool updates the JFIF density fields; for a PNG, it writes the standard pHYs physical-pixel metadata. The source pixels and compressed image data are copied as bytes, so the operation does not create another lossy JPEG encoding or require a browser canvas.
- Download a separate copy. Save the updated file and keep the original until it has been checked. The result is downloaded locally, and nothing is uploaded to a server. If an operation fails, the tool clears an old result link rather than presenting an earlier file as the new result.
- Verify the destination result. Open the downloaded copy in the layout program or print application where it will be used, place it at the intended size, and inspect small text, edges, and photographs. Attach that verified copy to the email and confirm that the recipient's workflow uses the expected physical size.
JPEG and PNG store the setting differently
JPEG and PNG can both carry print-density information, but they store it in different structures. The selected format therefore determines which field the changer updates.
| Format | Metadata written | What to check |
|---|---|---|
| JPEG | JFIF APP0 density fields using the standard dots-per-inch unit | If the source has no JFIF density header, the output adds a small JFIF header. An application may also display a resolution value from another JPEG metadata family. |
| PNG | The standard pHYs physical-pixel chunk expressed in pixels per metre | The page converts the requested DPI using the exact 0.0254 metre-per-inch relation. Integer pixels-per-metre storage can make a readback differ by a very small rounding fraction. |
These fields are defined in the W3C JFIF specification and the PNG specification. The storage difference explains why a PNG may show a slightly different DPI after download. That rounding fraction is a precision limit, not a change to the actual image pixels.
JPEG files can contain several forms of resolution information. A layout application may choose the JFIF value, an EXIF value, or another embedded instruction. The changer dynamically inspects standard EXIF resolution fields after selection, but it does not merge or rewrite every possible EXIF, XMP, ICC, IPTC, camera, GPS, or vendor extension. The updated JFIF or pHYs field is therefore documented, portable metadata for this focused operation, not a guarantee that every downstream program will interpret print size in the same way.
Input limits and what the operation does not change
The tool is deliberately limited to one JPEG or PNG at a time, with a 25 MiB input limit. It validates the file signature and bounded header structure before creating metadata. Truncated marker segments, malformed PNG chunks, duplicate physical-pixel chunks, and a pHYs chunk placed after image data are rejected rather than patched optimistically.
On a successful run, nothing is cropped, sharpened, enlarged, compressed, or converted. The output keeps the source pixel dimensions and compressed image data while updating the density instruction. Changing DPI is therefore not a way to make a blurry photo sharp or turn a low-resolution scan into a high-resolution print. Lowering the value does not delete pixels, and raising it does not invent them.
Use an image resizer when the actual pixel count needs to change. Keep the original file as a fallback, because print-density metadata is only one part of the final result and the destination application may make its own placement decision.
When the real goal is a smaller attachment
If the email is rejected because the attachment is too heavy, return to the encoded file size rather than its DPI. The DPI operation copies compressed image data and does not perform compression or a pixel resize, so changing the number alone will not solve a file-weight problem. Use an image resizer when a smaller pixel canvas is appropriate, or the Image Compressor when you need to reduce the encoded file while keeping the required format.
Those goals can be combined: first establish the intended print dimensions, then calculate the DPI, and separately resize or compress only when the recipient's size limit requires it. Follow the recipient's stated format and quality requirements, and inspect the result before sending it. No DPI value can substitute for missing pixels, a required export setting, or a final production check.
Check the result before it leaves your computer
Finish by testing the downloaded file, not just the original or the number you typed. Open it in the destination layout or print application, set the intended physical size, and look at small text, fine edges, and photos at final output dimensions. The metadata can guide the initial placement, but it cannot compensate for insufficient source pixels.
If the application reports a size different from your calculation, remember that it may be using another metadata family or its own layout rules. Confirm the actual placement in the application that matters, and keep the original until the attachment passes that check. Once the print size is right and the file meets the recipient's format and byte-size requirements, the DPI-adjusted copy is ready to send.
For a deeper look, see Image to Base64 for Email Attachment: MIME Steps.
For a deeper look, see Image to PDF for Email Attachment: Prepare One File.