Files stay on your device. Enter send · Esc close drawers

PWA Icon 512×512

512×512 PNG · maskable

Design assets often have to ship at a single canonical size — an icon set, a profile picture, a thumbnail — because platforms or frameworks will reject anything off-spec. PWA Icon 512×512 produces 512×512 PNG, the size the icon size expects.

Specifications

Output dimensions	512×512 pixels
Aspect ratio	1:1 (square)
Output format	PNG
Processing	100% in your browser — no upload
Cost	Free, unlimited
Source	Official guidelines

When you'd run PWA Icon 512×512

Replacing a generic placeholder with a hand-crafted asset at the correct 512×512 pixel size.
Sizing brand assets for client deliverables, design portfolios, or system-mockup exports.
Preparing assets for a CMS or template that requires a specific pixel dimension.
Generating consistent thumbnails or hero images across a content series.

About PWA installation icons and this preset

Audience: Progressive-Web-App installs across all major platforms.

How PWA installation icons ranks images: manifest-driven; the OS picks the closest size from the manifest icons array. Posting at the platform's exact native dimensions (512×512 px) preserves your original framing and avoids the softening that happens when the platform's own resampler runs to fit its expected size.

Platform-specific note: PWA installation icons at 512×512 are the canonical size for Android home-screen install prompts; iOS prefers 180×180 for Add-to-Home-Screen.

How PWA Icon 512×512 runs

This preset is a deterministic recipe — every step has fixed parameters so the result is byte-identical across runs of the same input.

Crop the image to a 1:1 aspect ratio. Mochi keeps the centre of the frame in the middle of the crop by default — drag the crop box if you want to recompose.
Resize to 512×512 px as PNG.

Where the work happens

PWA Icon 512×512 crops your input to 1:1 and resizes it to 512×512 px as PNG — a 262-kilopixel output. The work runs through canvas APIs and a WebAssembly image-encoder; the source image is decoded into an off-screen canvas, transformed in place, and re-encoded without any network upload.

Design deliverables to clients often require an exact pixel-size; this preset's deterministic output makes the deliverable repeatable. The browser-side path also means the file never leaves your device — relevant when the input contains personally identifiable information, screenshots of private documents, ID scans, or proprietary product photography.

Common mistakes

Generating only the 512×512 version when the platform also needs a 2× retina variant. Check whether you need a 1024×1024 export for HiDPI screens.
Submitting a JPEG when a transparent background is required. This preset outputs PNG to preserve transparency where the platform expects it.
Burning anti-aliased edges into a coloured background. Render your source on transparent first, then run this preset, so the icon edges blend cleanly on whatever surface it lands on.
Uploading sensitive images to a server-side tool. This preset runs entirely in your browser; the file never leaves your device. Verify this in your browser's network panel if working with confidential material.

FAQ

What does PWA Icon 512×512 output?

512×512 px, saved as PNG.

Why is the output square (1:1)?

The design this preset targets uses 1:1 framing. For passport photos this matches the printed-photo standard; for social posts it's the safe ratio that fills the feed without horizontal cropping.

Why PNG and not JPEG?

PNG preserves hard edges and transparency that JPEG would smear. Icons, logos, and screenshots compress better as PNG when the image isn't photographic.

Does my image get uploaded?

No. This preset runs entirely in your browser using WebAssembly + canvas APIs — no server round-trip. You can verify this in your browser's network panel: only static asset requests, no image upload. The file never leaves your device.

Related presets

Browse all recipes →