ImageConver · Day 17 · Browser icon tool
PWA Icon Generator
Generate standard 192×192 and 512×512 PWA icon PNG files and a ready-to-review web app manifest icon list. Choose fit, padding, and background, then download a local ZIP for integration and installation testing.
Local processing. The source image remains in this browser tab. Keep the editable master and validate generated assets in the platform’s official tools.
Choose an image to begin.
Direct answer
What this page produces and where it fits
Generate standard 192×192 and 512×512 PWA icon PNG files and a ready-to-review web app manifest icon list. Choose fit, padding, and background, then download a local ZIP for integration and installation testing. The package supplies general-purpose raster icons and manifest JSON. It does not create a full manifest, service worker, installability audit, maskable-specific artwork, monochrome icons, screenshots, shortcuts, or platform store assets.
Icon work is a delivery system, not a single resize. A platform may use the same identity in a store, launcher, notification, settings screen, browser tab, installed web app, shortcut, or operating-system search result. Each context can apply a different mask, density, cache, compositing rule, or validation step. The generated package should therefore be treated as a tested derivative of an editable brand master.
Begin with clean source artwork. Keep the primary subject centered, remove unnecessary text, avoid hairline details, and judge the design at the smallest real display size. Do not add a platform’s outer rounded mask or system shadow to the source unless current official guidance explicitly requires that treatment. A large preview can hide problems that become obvious at 16, 32, or 48 pixels.
File dimensions alone do not prove correctness. Confirm color space, alpha behavior, file paths, MIME types, manifest or asset-catalog metadata, purpose declarations, naming, cache behavior, and actual device presentation. Preserve the source file and document which generator settings produced the reviewed release assets.
Flusso di lavoro
A controlled four-step icon process
- 1
Inspect the source
Upload a high-resolution square source and choose a full-bleed background.
- 2
Choose settings
Set fit and padding while checking the 192-pixel and 512-pixel previews.
- 3
Generate assets
Generate icons and the manifest icon list in one ZIP.
- 4
Validate delivery
Integrate with the full manifest, serve over HTTPS, and test installation on target browsers.
Visual quality
Fit, detail, transparency, and recognition
Framing and padding
Fit mode changes meaning. Contain keeps the complete source and can add background around it; cover fills the square and can crop edges. Padding is useful for centered marks, but too much creates a small-looking icon. Compare masks and tiny previews before accepting a value.
Small-size detail
Raster downsizing removes detail. Thin strokes, small counters, photographic textures, and type can blur or disappear. The best small icon is often a simplified drawing rather than a mechanically reduced version of marketing artwork. Review the actual pixel output at 100% scale.
Background behavior
Transparency is not neutral. A browser, launcher, store, or operating system may composite transparent pixels against a color you did not choose. Full-bleed platform artwork should use a deliberate background where guidance expects one, while formats such as ICO may intentionally retain alpha.
Color contrast and recognition matter across light, dark, tinted, and themed environments. Test the icon near competing icons and against multiple backgrounds. Automated generation cannot determine whether a mark is distinctive, accessible, legally cleared, or consistent with current brand rules.
Important limits
What automated icon generation cannot guarantee
- Icons alone do not make a web application installable.
- General-purpose icons can appear letterboxed when a platform expects maskable artwork.
- Browser and operating-system installation behavior varies.
- The generated manifest fragment must be merged with a valid full manifest and correct deployment paths.
Use cases
Where this page fits in production
Product delivery
Add baseline install icons to a new progressive web app.
Compatibility work
Replace low-resolution manifest artwork.
Quality review
Generate consistent 192px and 512px PNG assets.
Developer handoff
Prepare a small integration package for a web development team.
Implementation
Configuration, caching, and release checks
Keep generated files at stable, cache-aware URLs. A manifest or HTML declaration that points to a missing file is not rescued by having the right PNG on a developer’s computer. Verify HTTP status, content type, dimensions, file bytes, and same-origin or cross-origin behavior where relevant.
Treat configuration files as reviewable code. Inspect every manifest entry, asset-catalog record, folder name, scale factor, purpose token, and filename before merging. A generated fragment intentionally avoids guessing application names, start URLs, bundle identifiers, theme colors, or project settings that belong to the real application.
Cache invalidation deserves a release check. Installed web apps, browsers, launchers, build systems, and stores can retain old icon resources. Use deliberate versioned paths or cache policy, rebuild the application, reinstall when necessary, and distinguish a stale resource from an incorrectly generated resource.
Validate both geometry and workflow. Geometry includes cropping, safe zones, centering, edge treatment, and small-size clarity. Workflow includes correct source control, repeatable settings, platform configuration, build output, deployment, and rollback. A visually attractive file can still fail because the project references a different filename.
Privacy
Local processing and asset handling
The browser reads the selected source with local file APIs, draws derivatives to canvas, encodes PNG data, and assembles the requested ZIP or ICO in memory. ImageConver does not send source pixels to an icon conversion endpoint in this workflow.
Local processing reduces transfer exposure but does not make a shared device private. Browser downloads, recent-file lists, synchronized folders, backups, extensions, and operating-system previews may retain copies. Use an approved workstation for unreleased brands or confidential product artwork.
Generated object URLs are temporary and are revoked when replaced or reset. Move reviewed assets into controlled project storage, retain the editable master, and close the tab after handling sensitive materials.
Common questions
PWA Icon Generator FAQ
Which PWA sizes are required?
Chromium guidance calls for at least 192×192 and 512×512 raster icons. Other sizes can improve platform-specific presentation.
Does the ZIP include a full manifest?
No. It includes the icons array fragment so you can review paths and merge it into your application manifest.
What purpose value is used?
The standard package uses purpose any. Create a separately tested maskable icon for purpose maskable.
Can I use an SVG icon?
Some browsers support SVG manifest icons, but raster PNG fallbacks remain important for broad compatibility.
Why use a solid background?
Transparent presentation may be composited differently by platforms. A deliberate full-bleed background gives predictable general-purpose artwork.
Do files leave my device?
No. All decoding, resizing, PNG encoding, JSON creation, and ZIP packaging happen in the browser.
How do I test installation?
Serve the manifest and icons from valid URLs over HTTPS, use browser developer tools, and install on representative desktop and mobile systems.
Primary references
Current platform documentation
- web.dev: Add a web app manifest
- W3C Web Application Manifest specification
- MDN: CanvasRenderingContext2D drawImage
Last reviewed: October 20, 2026. Platform requirements and tooling change; verify release-critical assets against current primary documentation.