Convertir una imagen
a 300 DPI

This image to 300 DPI tool changes print density metadata in a supported PNG or JPEG. It does not resize, sharpen, resample or recompress the picture. The useful question is whether the existing pixels cover the intended physical size. A density tag tells compatible software how to interpret those pixels; it cannot provide detail that the original file does not contain.

Although interfaces often call the tag DPI, image pixel density is more precisely PPI. Printer dot patterns are a separate output process. For a 1500 pixel width, the nominal width at 300 PPI is five inches. Changing an old 72 DPI declaration to 300 changes the suggested print scale, while the width remains exactly 1500 pixels. It does not turn that file into a larger raster image.

PNG stores physical density as integer pixels per metre. This tool writes 11811 for both axes with a metre unit, approximately 300 PPI. Supported JPEG uses the JFIF inch unit and values of 300 on both axes. Files declaring non-square pixels are rejected because replacing unequal densities could change their intended aspect ratio. Conflicting EXIF resolution fields, XMP and Photoshop metadata are also rejected rather than guessed.

The edit preserves PNG IDAT data or JPEG compressed scan data and retains other non-target bytes in accepted files. The file size may still change when a PNG density chunk is added. This is not a format converter or a private metadata remover. Color profiles and supported EXIF information remain present; check those separately if your delivery requirements include color conversion or removal of identifying fields.

Keep the original image and determine the final print dimensions before processing. If a printer asks for an 8 × 10 inch image at 300 PPI, the corresponding raster dimensions are 2400 × 3000 pixels. Check the actual source dimensions in your image software. A filename containing “high resolution” or a current 300 DPI label does not establish that enough pixels exist.

Choose one PNG or JPEG using the file control. The maximum is 20 MiB, meaning 20 × 1024 × 1024 bytes. A familiar extension does not make a file supported: the tool reads its structure and density declarations. If an error appears, no output is created. Keep the original and read the reason before deciding whether to export a compatible copy in your normal image editor.

Review the encoded pixel dimensions, original density and nominal size at 300 PPI. These axes follow the encoded file. If EXIF orientation is present and supported, it is retained rather than applied as a rotation. An application that honors orientation may display the long edge in a different direction. Use the orientation notice and inspect the actual picture before treating width and height as final page orientation.

Select “Set 300 DPI metadata” after reviewing the inputs, then download the prepared copy. Choosing a file alone does not trigger that final download. The original file on your device is not edited in place. Open the downloaded copy in an image application, compare its pixel dimensions and inspect its density or physical size. Some software ignores density metadata or overrides it with a placement size, so check the final document too.

Processing and input file bytes remain in the browser. Sharing a calculation summary does not transfer the selected picture; the recipient must choose their own file. A shared URL can still expose any included settings through the page request and server logs. Keep file contents, personal identifiers and private document information out of URLs. For publishing, finish by checking the complete artwork against the service's actual file requirements.

This table is arithmetic at a chosen density, not a set of guaranteed printer presets. Each dimension divides evenly by 300, making the relationship easy to check without rounding. It describes pixel counts and nominal physical sizes, not paper margins, bleed, printer capability or the amount of detail captured in a photograph. Choose a row only when it matches your actual intended artwork area.

For a different size, calculate each axis separately. Maintaining width while changing height can distort the image, and cropping to a different aspect ratio removes pixels. Neither operation happens in this tool. If the final layout crops the image, assess the remaining pixels rather than the original file dimensions. A 300 PPI label on the source does not compensate for a heavily cropped placement.

The millimeter column uses exactly 25.4 millimeters per inch. PNG's stored density is the nearest integer representation, so software reading the exact tag can report a tiny difference from these nominal values. That is a storage precision issue rather than a missing pixel or a need to resample. Use the intended placement dimensions and confirm the final export with the printer instead of repeatedly changing the tag to chase a display rounding difference.

A 1500 × 2100 image with an old 72 DPI tag

Assume a supported square pixel image with 1500 × 2100 encoded pixels. At 72 PPI, software might suggest 20.8333 × 29.1667 inches. At 300 PPI, the nominal dimensions become 5 × 7 inches, or 127 × 177.8 millimeters. The output still contains 1500 × 2100 pixels. This edit is useful when the intended placement is five by seven and the metadata is wrong. It does not establish that the source is in focus, correctly exposed or suitable for every printing process. Inspect the downloaded copy and its final placement.

An 8 × 10 request with too few source pixels

Assume the requested output is 8 × 10 inches at 300 PPI, but the source contains 1200 × 1500 pixels. The required count is 8 × 300 by 10 × 300 = 2400 × 3000. The existing file supports only 4 × 5 nominal inches at 300 PPI. At an 8 × 10 placement its effective density is 150 PPI. Changing the tag cannot double either axis. Obtain a larger original, accept a smaller print, or discuss the actual requirement with the printer; this tool offers no upscaling step.

Understanding the PNG integer density value

Assume a supported PNG with square pixels and no conflicting resolution metadata. The ideal pixels per metre value is 300 ÷ 0.0254 = 11811.023622…. PNG requires an integer, so the tool stores 11811. Multiplying back gives 11811 × 0.0254 = 299.9994 PPI. A rounded application display of 300 and an exact display of 299.9994 can therefore describe the same output file. The difference is not repaired by running the tool repeatedly. These examples explain metadata arithmetic and placement choices; they are not claims of printer acceptance or a measured improvement in image quality.

Do not rename a HEIC, WebP or TIFF file to JPEG and expect compatibility. An extension changes the label, not the container structure. Use an image editor when actual format conversion is necessary, and understand whether that export resizes, recompresses or changes color. Those operations are separate from this tool's metadata edit and may affect a file in different ways.

Do not confuse local processing with removal of private information. An accepted file retains non-target metadata, including supported orientation and location fields. A rejected file with EXIF resolution needs a compatible export workflow, not an assurance that all EXIF is broken or unsafe. Keep originals when creating another version so you can inspect exactly which changes your separate editor makes.

Finally, verify the placed image in the exported document. Layout software can scale a correct source beyond its useful pixel density or ignore its embedded print size. For a book project, use the cover size calculator for canvas geometry and check your publishing requirements independently. Neither a new density tag nor a correct cover dimension supplies missing detail, fixes a barcode or guarantees print approval.