Resize image to 512×512
1:1 · 0.26 MP · prints at 4.3×4.3 cm at 300 dpi
- No upload
- Exact target size
- Batch ready
Drag images here, or click to choose
JPG / PNG / WebP / HEIC · up to 25MB each · batch supported
Files never leave your device — everything runs in your browser.
Progress
That file could not be processed
What 512×512 is used for
- PWA and Android app icons
- Marketplace preview images
- Discord and Slack custom emoji
- Model and asset thumbnails
1:1, 0.26 MP. Icons need to stay under a few hundred KB each — the same 512×512 PNG can be 8 KB or 400 KB depending on how much detail it carries.
Pixels are not DPI
A file with 512×512 pixels carries no physical size until someone prints it. At 300 dpi that is 4.3×4.3 cm; at 150 dpi it is twice as large and half as sharp. Forms that ask for “300 dpi” and “512×512 px” are asking for the same thing in two languages — this tool satisfies both, and stamps the requested dpi into the file.
Why it will not upscale by default
Padding a 400×300 image to 1920×1080 does not add detail: it invents pixels by interpolation, and the result looks soft at every zoom level. The upscale switch exists for the cases where you truly must (a platform that rejects anything smaller), but the honest answer is to start from a bigger source.
Cropping, not stretching
Changing the aspect ratio is a destructive decision. “Cover” fills the frame and cuts the overflow; “contain” keeps everything and adds padding; “stretch” distorts on purpose. Default is cover with a centre anchor, which is right for photos and wrong for documents — pick per batch.