Six Destinations, Three Formats, One Pixel Size
512 × 512 is unusual among resize targets: it is not a marketplace size, not a print size, and not a social-media tile — it is the number where app stores, chat platforms, web standards and AI models all happened to land. Each destination reuses the same 262,144 pixels but applies a different format, transparency and file-size rule, which means the same 512 × 512 file is almost never valid for two destinations at once. The table below is the compliance matrix no single competitor page publishes:
| Destination | Format | Transparency | Max file | Source |
|---|---|---|---|---|
| Google Play icon | PNG (32-bit) | Required (alpha for adaptive mask) | 1,024 KB | Play Console Help |
| WhatsApp sticker | WebP | Required (floats on chat bg) | 100 KB static / 500 KB animated | WhatsApp FAQ 1056840314992666 |
| PWA manifest icon | PNG | Optional (maskable needs safe area) | No hard limit (keep under 512 KB) | MDN / web.dev |
| Stable Diffusion 1.5 | Any (PNG/JPG/WebP) | N/A (model input) | N/A (decoded to latent) | SD1.5 training resolution |
| Discord server icon | PNG / JPG / GIF | Optional | 10 MB | Discord support |
| Telegram sticker | PNG (static) / WebP/TGS (animated) | Required | 512 KB static / 64 KB animated | Telegram sticker docs |
The conflict is visible in the table: Google Play wants PNG with alpha, WhatsApp wants WebP with alpha, PWA wants PNG, and if you are also shipping an Apple App Store icon at 1024 × 1024 the alpha rule flips entirely — Apple forbids transparency and rejects the build with ITMS-90717. The same designer working across Android and iOS at adjacent power-of-two sizes must export twice: once with alpha (512 for Play) and once without (1024 for Apple). No competitor page connects these two rules because they live in separate documentation trees.
The WhatsApp 100 KB Trap: Pixels and Bytes Are Independent Constraints
Most 512 × 512 resize pages handle the pixels and stop there. WhatsApp enforces two simultaneous constraints: the image must be exactly 512 × 512 pixels AND each static sticker must be 100 KB or less. These are independent — a 512 × 512 WebP of a flat vector illustration compresses to 20–30 KB easily, while a photographic sticker with fine gradient detail can hit 120 KB at quality 80. The pixel dimension is non-negotiable (WhatsApp rejects anything other than 512 × 512 at import), so the only lever is quality and content simplification. Practical sequence: resize to 512 × 512 as WebP, check the file size, and if over 100 KB lower quality to 70–75 or remove background detail at full resolution before resizing — batch background removal at the original resolution produces cleaner cutouts that compress better than 512-px-first removal. For animated stickers the ceiling is 500 KB and 10 seconds, which is a separate budget entirely. The tray icon is a third asset: 96 × 96, under 50 KB, PNG — most sticker pack rejections come from forgetting the tray icon, not the stickers themselves.
The Power-of-Two Chain: 256 → 512 → 1024 → 2048
512 is 2^9, which places it in a binary chain where each step doubles: 256 (2^8, web icons and Discord emoji display) → 512 (2^9, this page) → 1024 (2^10, Apple icon master and SDXL native) → 2048 (2^11, Shopify display-best). This is not numerology — GPU texture pipelines, VAE latent compression (factor 8, so 512 px → 64 × 64 latent) and diffusion-model training all use power-of-two dimensions for memory alignment. Stable Diffusion 1.5 was trained at exactly 512 × 512 for its full training run; SDXL-Turbo is optimized for 512 × 512 as its fastest inference mode (1–4 steps, 0.5–2 seconds on an RTX 3090). If you are building an AI reference pipeline, normalizing inputs to 512 for SD 1.5 or 1024 for SDXL produces the cleanest compositions — deviating far from the training resolution causes repeated subjects, composition drift and attention bleed. The same chain matters for icon ladders: a 1024 master downscaled to 512 here and to 256 downstream gives you three sizes from one export, and the bulk image resizer processes all three in one pass.
Crop, Pad, or Fit: Feeding Rectangles Into a 512 Square
Most 512 × 512 inputs are not born square. Phone photos arrive 4:3 or 3:2, screenshots come in landscape, and sticker art is often drawn at non-square ratios. Three options, each correct for a different destination:
- Center-crop (Cover): scales the image to fill the 512 square and trims overflow from the center. Best for Google Play icons (the subject should fill the frame) and AI model inputs (blank borders shift diffusion attention). Loses up to 33% of a 3:2 frame.
- Pad to fit (Contain): fits the whole image inside 512 × 512 with bands of fill on two sides. Best for WhatsApp and Telegram stickers (the art floats, padding is transparent), PWA maskable icons (safe area inside the inner 80%), and logos that must not be cropped. PNG and WebP padding is transparent; JPEG padding is white.
- Stretch: forces the image to 512 × 512 by distorting proportions. Never correct for photos or icons; only viable for near-square abstract textures where the distortion is invisible.
For sticker workflows, always remove the background before resizing, not after — edge detail computed at 6000 px beats edge detail computed at 512, and the background removal page explains why the order is non-negotiable. For PWA icons, keep critical content inside the inner 80% of the canvas (the maskable safe zone) so Android's adaptive cropping does not clip your logo — the bulk screening tool can audit a folder against this rule before export.
A 512 Batch Pipeline (Icon Set, Sticker Pack, or AI Reference Folder)
- Decide the destination first: Google Play icon (PNG with alpha, opaque corners), WhatsApp sticker (WebP with transparency, 100 KB cap), PWA manifest (PNG, maskable safe area), or AI reference (PNG/JPG, center-crop preferred).
- Clean backgrounds before sizing if needed — batch background removal at original resolution, especially for stickers and transparent icons.
- Resize the whole folder here: exact 512 × 512 for squares, pad or crop for rectangles. The tool locks to 512 × 512 and applies the same mode to every file.
- Export in the destination's format: PNG at quality 100 for Google Play (truecolor 32-bit), WebP at quality 80 for WhatsApp stickers (check file size, drop to 70 if over 100 KB), PNG for PWA, JPEG q85 for AI references.
- Download the ZIP. For a sticker pack, also export a 96 × 96 tray icon separately. For an icon ladder, repeat at 1024 and 256 — filenames preserved across runs.
For final file-weight tuning — especially the WhatsApp 100 KB ceiling — run the ZIP through the batch compressor in one deliberate pass rather than re-encoding repeatedly, since each JPEG or WebP generation costs quality. If your 512 × 512 images are destined for a marketplace listing instead of an icon or sticker, you are on the wrong page: marketplace sizes start at 1000 × 1000 (Amazon zoom floor) and go up to 2000 × 2000 and 2048 × 2048.