Hundred-pixel widgets and micro profile boxes
Legacy profile widgets and badge rails still publish 100×100 as a hard box. Near-miss exports fail even when the preview looks fine on a phone. Scale to exact 100×100, confirm width and height on the result card, and only then open a compress sibling if the same form also names a kilobyte ceiling.
Source masters that survive downscaling to 100×100
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. Do not upload documents your organization forbids processing online; prefer offline tools when policy requires it. 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.
Micro square avatars at one-hundred-pixel checkpoints
Tiny square boxes appear on legacy profile widgets, upscaling blurry sources shows immediately at this size. Pixel boxes and kilobyte caps are independent validators, satisfying one never excuses the other. Start from the original export whenever you still have it, not a chat-compressed copy. If the result looks too soft, tighten framing before lowering quality again.
JPEG output for hundred-pixel profile slots
Default JPEG output keeps bytes practical for photo content. PNG logos may flatten when JPEG keeps widget bytes low. Very large source dimensions fight small byte budgets; the engine may reduce width and height when quality alone fails. Preview against both light and dark backgrounds when edges or transparency may change after encoding. If the result looks too soft, tighten framing before lowering quality again.
Kilobyte caps after 100×100 pixel fit
After pixels match, some widgets still cap weight near ten kilobytes, open KB siblings when a second rule appears. Very large source dimensions fight small byte budgets; the engine may reduce width and height when quality alone fails. Preview against both light and dark backgrounds when edges or transparency may change after encoding. If the result looks too soft, tighten framing before lowering quality again.
Batch badge icons at one-hundred-pixel squares
Each icon previews independently, thin strokes vanish when downscaled from oversized masters. Match the published width×height first when both rules appear, then return for weight targeting if needed. Start from the original export whenever you still have it, not a chat-compressed copy. Temporary processing is not archival storage, save the download you intend to submit.
Verify hundred-pixel output on the submission phone
Open download locally; widgets rarely show EXIF-corrected orientation after re-encode. Match the published width×height first when both rules appear, then return for weight targeting if needed. Related pages handle neighboring ceilings so you are not stuck forcing one target. Portals care about clearing the limit more than hitting a precise byte total.
How the resize is applied
Output is written at 100×100 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
Must avatars be exactly 100×100?
Output targets the micro square box, read final pixels on the result card. JPEG target-size encoding is lossy; the preview exists so you can judge tradeoffs honestly.
100×100 resize fix kilobyte errors?
Not always, some widgets add tiny KB caps after pixel checks. JPEG target-size encoding is lossy; the preview exists so you can judge tradeoffs honestly.
Upscale logos to 100×100?
Soft results are common, design near target size when possible. If softness is unacceptable, crop tighter or ask whether a higher official limit exists.
Orientation after 100×100 resize?
Trust preview orientation; EXIF tags may not match display. Batch mode still shows per-file previews. Review each result before submitting a set.
Batch icons to 100×100?
Each icon previews independently at the same square target. Open the download once on your submission device before retrying the portal. JPEG target-size encoding is lossy; the preview exists so you can judge tradeoffs honestly.
Why not generic resize?
Generic resize works broadly, this page names the exact box so search intent matches the checklist. Open the download once on your submission device before retrying the portal.