Seal Size and Resolution Guide: Pixels, Millimeters, and DPI
A seal can look perfectly sharp in the editor and still end up blurry, tiny, or unexpectedly large in a document. The usual cause is not the design itself but a mismatch between three measurements: pixels, millimeters, and DPI. Once you know which one controls each stage, sizing becomes predictable.
Pixels, millimeters, and DPI do different jobs
- Pixels (px) describe how much image detail a PNG contains. More pixels allow the image to remain crisp at a larger displayed or printed size.
- Millimeters (mm) describe the physical size you want on a page.
- DPI tells print software how densely to place those pixels. It connects pixel dimensions to physical dimensions; it does not add detail that is missing from the source image.
The conversion is:
pixels = millimeters ÷ 25.4 × DPI
For example, a 40 mm seal at 300 DPI needs about 472 pixels across. A 20 mm mark at the same resolution needs about 236 pixels. Rounding by a pixel or two is harmless.
Choose the final use before the export size
For a slide, website mockup, or on-screen approval sheet, think mainly in pixels. Export at least as large as the seal will appear; using a 2× image can keep it crisp on high-density screens.
For Word, PDF, or printed artwork, start with the intended physical width. If a recipient, printer, or internal brand guide specifies a size, use that requirement rather than a generic preset. For ordinary office printing, 300 DPI is a practical working target; lower values may be enough for screen-only documents, while professional production may ask for something different.
In the online seal generator, switch the size control to mm + DPI when physical output matters. The editor calculates the required pixels for you. If you are exploring layouts first, the template gallery provides starting points that you can resize and customize.
A simple workflow for documents and print
- Decide the finished width. Measure the space on the document or ask the printer for the required dimensions.
- Set millimeters and DPI. Enter both values before fine-tuning text and borders, because very small output can make thin details hard to read.
- Export with enough detail. PNG is convenient for office documents; SVG stays sharp at any size when the destination accepts vector artwork. See SVG vs. PNG for seals for the trade-offs.
- Place the image at the intended physical size. Do not assume an app will interpret image DPI metadata consistently. Set the width explicitly in Word, your PDF editor, or layout software.
- Check at 100% and print a proof. Confirm that small text, thin rings, and distressed textures survive at the real output size.
Our guide to adding a seal to PDF or Word covers image wrapping and placement after export.
Common sizing mistakes
- Making a small PNG larger in the document. Enlarging changes its displayed size but cannot recreate lost edge detail. Re-export at a larger pixel dimension instead.
- Using 4× export without changing the placed size. A higher-resolution file is useful only when the document keeps the same physical width; otherwise the seal may simply appear four times larger.
- Treating DPI as image quality by itself. A 160-pixel image labeled 600 DPI still contains only 160 pixels. Pixel dimensions and final physical size matter together.
- Judging only from a zoomed preview. Thin lines that look fine at 300% zoom may disappear or fill in when printed at actual size.
- Adding a white box around the seal. For document overlays, use a transparent background. The steps are in how to create a transparent PNG seal.
Quick pre-export checklist
- Final width is known in pixels or millimeters.
- PNG pixel dimensions are large enough for that width.
- Text and borders remain readable at actual size.
- Transparent background is enabled when the seal must overlap content.
- The destination supports the chosen format.
- A proof has been checked in the real document, not only in the generator.
Size is part of the design. Set it early, verify it at the final scale, and you will avoid most blurry-export and oversized-document problems.