Resize an image to 64 × 64 pixels
The 64 × 64 box and PNG output are preset: the page maps your logo or mark onto that exact square and hands back a small, lossless icon file — built in your browser, nothing up anywhere.
Your images
Settings
Set both for an exact pixel size; set one and the other scales to keep the ratio.
Generated images
- Nothing uploaded
- Free, no sign-up
- Strips EXIF
- Batch files
64 pixels is the size where an icon stops being a picture and becomes a symbol. The browser tab strip draws favicons around 16 to 32 px, but most icon pipelines — Android adaptive-icon masks, old Windows shortcuts, game tiles, pixel-art thumbnails — still ask for a 64 × 64 source as the smallest square that holds a recognizable mark. You have the 1024 × 1024 logo file; you need the little one, and the design tool for a single 64 px square is overkill for a file that will be a few kilobytes.
This page is the short path. The box is locked at 64 × 64 and PNG is preselected, because an icon needs its alpha channel intact and losslessness — a 64 px logo encoded as JPG comes back with ringing around the edges and a gray haze in the corners that a 1024 px original never had. The mapping is direct: a square logo lands square; a wide mark fills the box, so anything with a ratio farther from 1:1 than about 2:1 gets stretched past what reads as the same mark.
Drop one file or a whole folder of marks. The queue processes each one at the same box and hands back a .zip in the order you added them. The decode and the resize happen on your own machine, and the original 1024 px file stays exactly as it was on disk.
How it works
Two things are already set — the 64 × 64 box and PNG — so the job is choosing which marks to shrink.
Add the logos
Choose the file, drag it on, or paste with Ctrl+V. A PNG with transparency is the cleanest source; a JPG works but arrives with a solid background, and an SVG is drawn to pixels first, so its crispness is lost at 64 either way. A folder of marks queues up the same way.
Check the two settings that matter
The width and height fields read 64 and 64, and the format bar sits on PNG. If your mark is not already square, press the crop button on the card first — it opens a square, center-locked box over the logo — so the 64 × 64 output carries the mark instead of a flattened strip. Leave everything else alone; the quality slider is not in play on a lossless PNG.
Generate, look at it, download
Press Generate images and open the Compare slider on the card: at 64 px you are judging a symbol, and the two pixels that survived are the ones that matter. If the mark reads, save it; if it does not, the fix is a bolder logo, not a second pass. A batch comes back as one .zip.
What 64 × 64 is actually used for
The number shows up in places that stopped advertising it but still enforce it:
- Favicon source: the .ico entry and the tab strip scale it down to 16 or 32 px; 64 is the smallest square that keeps a mark readable there
- App-icon bases for Android, Windows and Linux shells that sample down from a master square
- Game and forum tile slots: older engines and forums that list 64 × 64 as the exact accepted square
- Thumbnail rails in dashboards and admin panels that hardcode a 64 px grid
- Pixel-art handoff: the source size for an artist who will further reduce it, or a sprite sheet's row height
Why PNG wins at this size
At 1024 px, the format question is mostly weight. At 64, it is edges. A logo on a transparent background needs the alpha channel, which only PNG, WebP, GIF and a few others carry — and JPEG's compression artifacts scale with how much you squeeze a small area, so a 64 × 64 JPG of a crisp mark shows the halos that nobody can see at full size. PNG is lossless: the 64 pixels that come out are exactly the 64 pixels the resampler decided on, with the transparent corners staying transparent. The file lands in a few kilobytes, which is irrelevant on any modern connection but relevant on the old intranet it may end up on.
A wide logo in a 64 × 64 box
The box does not letterbox. A 2000 × 500 wordmark mapped onto 64 × 64 comes out flattened to a quarter of its intended height — the tool cannot know which pixels were the part of the mark. If the asset is wider than tall, crop to the square region that is the mark (the icon button on the card does exactly that, locked 1:1 and center-placed), and only then run the resize. The same advice goes for a tall portrait: pick the square that reads as the symbol, or commission a dedicated 1:1 mark at this size — that is what icon designers charge for, and the square crop here is the honest DIY version.
What the 64 px version will not show you
Detail below about two pixels wide does not survive the reduction — a thin-stroke letterform, a dot grid, a hairline border. This is a property of 64 pixels, not of this tool: the resampler averages the source into the target and there is no setting that adds what was already smaller than the target. If the mark depends on a 1 px line, the 64 px output has a 1 px line; if it depended on a 0.5 px gap, the gap is a color now. The Compare slider on the card is the honest preview of that averaging — trust it over the full-size original.
Frequently asked questions
Will a 500 × 200 logo come out stretched to 64 × 64?
Yes — the box is literal and fills both dimensions. Crop to the square that is your mark first (the crop button on the card, locked 1:1, generates the square out of the middle), then let the box shrink it. Without the crop you are exporting a squashed strip, which is the most common mistake at this size.
Do I get a 16 × 16 and a 32 × 32 as well?
No — one 64 × 64 file. Browsers and app shells scale it down to whatever pixel size the tab or grid needs. If a specific platform hardcodes 32 × 32, run the same page at 32 by typing 32 in the width and height fields — the rest of the flow is identical.
Why does my logo look slightly softer at 64 than at 1024?
Downsampling averages groups of source pixels into each target pixel, so some of the original edge sharpness is traded for a cleaner 64 px result — that is the resampler working, not a defect. If it reads as mush rather than clean, the source mark was too intricate for 64 pixels and the fix is a bolder redraw, not a different setting.
Can I keep the transparency?
Yes — the PNG output carries the alpha channel, so corners that were see-through in the source stay see-through at 64. A JPG source has no transparency to begin with, and the page fills the background white in that case; swap in the PNG master from your design file if you need the clear corners.
My mark is a photo, not a logo. Will 64 px do it?
A face or a product at 64 pixels is a thumbnail, and this page will happily map it onto the box — but a photo needs more pixels than a symbol does to stay legible. For a face, 512 × 512 or 192 × 192 is a more useful target; 64 is where logos live, not portraits.
Is the file uploaded to make the 64 px version?
No. The decode, the square mapping and the PNG write all happen in your browser on your device. The original on disk is not touched, and nothing about the request travels to a server — there is no server in the loop.