Images & photos · Social Image Resizer
Pixels, DPI and Device Pixel Ratio: What 'Resolution' Means on Screens
· Background
image-resolution pixels image-resizing
Print habits say 300 DPI, but social platforms ignore DPI entirely and care only about pixel dimensions and how the device scales them. This post untangles pixels, points, DPI metadata and device pixel ratio so you stop exporting the wrong thing.
The '300 DPI' image that was still blurry — the concrete confusion of applying print rules to a screen
An image labelled 300 DPI can still look soft on a screen if it contains too few pixels for the displayed area. DPI connects pixels to a physical print size; it does not manufacture samples. Social Image Resizer asks for output width and height in pixels and never offers a DPI field.
That interface choice defines the product contract. A current portrait preset is 1080×1350 pixels, and custom ratio mode derives integer pixel dimensions from a longest edge. The encoder writes a new image from the canvas. The code does not read, preserve or let the user edit a print-density tag.
DPI metadata is outside this tool’s controls; output geometry is defined in pixels
For print, dividing pixel dimensions by a chosen dots-or-pixels-per-inch value estimates physical size. That relationship can guide printers, but the same file can carry different density metadata without gaining or losing pixel samples. A 1200×1200 image remains 1,440,000 pixels regardless of a changed print tag.
This article corrects the outline’s stronger claim that screens never read DPI in all circumstances. The repository does not test every browser, application or CSS image behavior. What it proves is that ToolAcre’s framing arithmetic uses bitmap and target pixel dimensions, not DPI metadata.
The 72 DPI history is outside repository evidence and is omitted
The familiar 72 DPI story belongs to display history, but no cited source for that history appears in the tool repository. Repeating it would turn an outline into an unsupported fact. For this workflow, the useful lesson is independent: a density label and a pixel grid are different pieces of information.
If historical provenance matters, consult a sourced display-history reference. If a social crop matters, inspect width and height. Keeping those questions separate prevents a print-era label from distracting reviewers from the actual target canvas and from the scale at which the image is shown.
Device pixel ratio — why a phone's logical points are backed by two or three physical pixels, and what that means for how large your image needs to be
Device pixel ratio relates CSS display units to physical device pixels. A responsive page may show the same CSS-sized element with more hardware pixels on a denser screen. ToolAcre uses devicePixelRatio for its on-screen preview canvas, while exportTarget renders separately at the target’s full output dimensions.
That separation avoids confusing preview backing resolution with downloaded file size. A high-density phone can make the preview canvas crisp, but it does not silently multiply the export preset. The results table reports the actual file dimensions, which are the correct values to hand to another workflow.
Destination handling of DPI and upload dimensions must be verified externally
The workbook says platforms ignore DPI and resize to their own dimensions. Destination behavior is outside the repository, so this article does not universalise it. Consult current destination guidance and inspect the live result. ToolAcre can guarantee only the pixel dimensions of the local canvas output.
When a destination requirement is written in pixels, match those pixels or a currently documented alternative. If a print workflow also consumes the file, manage its density metadata in an appropriate tool. One derivative may not satisfy both use cases merely because a DPI number sounds large.
Worked example: compare pixel dimensions while holding unsupported DPI claims aside
Create two test exports from the same source: one current 800×800 profile preset and one 1080×1080 square post preset. Compare them at equal CSS display size and at one-to-one pixels. The larger grid gives the renderer more source samples to work with, although visible benefit depends on display and content.
Do not change or claim a DPI tag in this exercise because ToolAcre exposes no such control. Record only dimensions, format, measured bytes and observed appearance. That evidence demonstrates what the tool actually changed and avoids attributing sharpness to metadata that was neither inspected nor selected.
What this does not cover — print production and colour proofing, where DPI does matter
Print production, physical proofing and colour management remain separate. Printers need physical dimensions, substrate knowledge and an appropriate pixel density; this cropper does not calculate those requirements. Its content also warns that unusual source colour profiles are not preserved through canvas.
Use a print-specific application when inches, centimetres, bleed or proof profiles matter. Use Social Image Resizer when the job is a pixel rectangle for a screen-oriented placement. Clear boundaries prevent a successful social export from being mistaken for a press-ready master.
Takeaway: think in pixels — the Social Image Resizer works in pixel dimensions and aspect ratios, which is all a screen ever sees
Think in pixels for this tool because pixels are the inputs to every framing equation and the dimensions of every output canvas. Treat DPI as separate print metadata unless an audited destination contract says otherwise. Device pixel ratio affects how the browser presents its preview, not the named export target.
Choose a current preset or custom pixel size, inspect the downloaded dimensions and test at the intended display scale. That workflow resolves the practical question without myths. A large DPI label cannot compensate for a small source, while an explicit pixel grid gives reviewers a measurable artifact.