App-list icons at 128×128
Desktop and launcher lists commonly reserve a 128×128 icon well. Oversized marketing art looks soft when forced into that well without a clean square crop first. This tool targets 128×128 pixels so the download matches the published box, not an approximate export from a design canvas.
Source masters that survive downscaling to 128×128
Start from a larger master when possible; upscaling a tiny source makes edges fuzzy even if pixels match. Prefer a clean master with more pixels than you need when downscaling; upscaling tiny sources cannot invent detail. Temporary server copies are cleaned on a schedule; treat downloads as your durable copy. Related pages handle neighboring ceilings so you are not stuck forcing one target. Width and height on the result card update whenever the engine changes dimensions.
One-hundred-twenty-eight-pixel app and extension icons
Chrome extensions and legacy mobile icons cite 128×128 as a minimum crisp grid for store listings. Very large source dimensions fight small byte budgets; the engine may reduce width and height when quality alone fails. Evenly lit, face-forward crops usually survive tighter budgets better than wide scenes. Being under the cap is the real pass condition; exact byte matching is uncommon.
Fill cropping on 128×128 square icons
Logos near frame edges get trimmed on fill, center glyphs with margin before export. Shoulders-up framing on a plain backdrop spends scarce bytes on the subject reviewers must recognize. Use one clear filename and extension so portals do not reject odd suffixes. If the result looks too soft, tighten framing before lowering quality again.
Format notes for 128×128 store icons
Default JPEG output keeps bytes practical for photo content. Flat illustration may need PNG source before JPEG resize when edges must stay sharp. Families, product variants, and localized banners compress differently with identical settings. If rejection continues, re-read the help text for a second hidden rule. Width and height on the result card update whenever the engine changes dimensions.
Weight limits beside 128×128 checklists
Store consoles sometimes cap PNG or JPG bytes separately from pixel validation, read both lines in the spec. Keep an uncompressed master until the destination accepts the file. Avoid screenshotting the preview pane, download the generated file instead. When format or pixel rules sit outside this page, finish those steps on the related tools linked nearby.
Batch extension icons at one-twenty-eight pixels
Each variant preview separately, dark-mode and light-mode assets need independent legibility checks. Match the published width×height first when both rules appear, then return for weight targeting if needed. Evenly lit, face-forward crops usually survive tighter budgets better than wide scenes. Temporary processing is not archival storage, save the download you intend to submit.
Submission check for 128×128 manifests
Confirm pixels on the result card match the integer in package.json or store JSON before publishing an update. Start from the original export whenever you can; chat-downloaded copies often arrive already soft. Open the download once before you close the tab. Width and height on the result card update whenever the engine changes dimensions.
How the resize is applied
Output is written at 128×128 pixels. The preview and download use that raster. File weight still depends on subject detail and the output format, not only the pixel box.
Resize checks
Exact-size tools are checked by measuring the output width and height after processing. A pass means those pixels match the named box. File size is reported separately. Reviewed 5 October 2026.
Technical reference
Everyday “JPEG” files follow the JFIF interchange pattern on top of JPEG compression. MDN summarizes the type, MIME value image/jpeg, and common extensions: MDN image file type guide.
Frequently asked questions
128×128 required for extension icons?
When store JSON cites 128×128, match pixels then handle any separate weight cap. Re-read format, pixel, and kilobyte lines together, validators often check more than one.
128×128 alone enough for store upload?
Console validators may still cap PNG or JPG bytes, read the full spec. Neighboring tools exist for nearby sizes; switching is better than forcing the wrong ceiling.
Upscale art to 128×128?
Possible but edges soften, start from the largest master available. If softness is unacceptable, crop tighter or ask whether a higher official limit exists.
EXIF rotation after 128×128 resize?
Trust on-page preview before download; tags may be stripped on re-encode. Neighboring tools exist for nearby sizes; switching is better than forcing the wrong ceiling.
Batch icons at 128×128?
Each theme variant gets its own preview and download at the target box. If softness is unacceptable, crop tighter or ask whether a higher official limit exists.
Generic resize versus 128×128 tool?
Generic resize works broadly, this page names the exact box so search intent matches the checklist. If softness is unacceptable, crop tighter or ask whether a higher official limit exists.