Manifest validation
Catch invalid colors, unsupported display modes, malformed resource paths, and launch URLs that fall outside the declared scope.
Turn any web experience into a more app-like experience with a polished manifest, adaptable icons, and confident configuration.
Configure every detail and see what your visitors will get.
Give the experience a clear identity users will recognize.
Customize launch behavior and browser surfaces.
Generate launcher assets in all the essential sizes.
Using a sample icon — replace before publishing.
Optional metadata, shortcuts, and existing manifest imports.
Shortcuts can be displayed in the installed app's context menu on compatible platforms.
A beautiful experience.
Checking your configuration…
Install prompts depend on browser rules, HTTPS (or localhost), valid hosted icon URLs, and other site behavior. A manifest alone does not provide offline caching. Set your actual deployment manifest URL to validate origin and path accurately.
Bundle includes the manifest, PNG icons, and setup instructions.
Catch invalid colors, unsupported display modes, malformed resource paths, and launch URLs that fall outside the declared scope.
Export dedicated 192px and 512px launcher icons and a padded maskable variant that respects the standard safe zone.
Bring an existing JSON manifest, preserve unfamiliar fields, adjust the basics, and export assets without sending data to a server.
Not necessarily. Installation and promotion rules differ by browser and may require HTTPS or localhost, a suitable icon, working routes, and other conditions. Offline behavior requires separately implemented caching, commonly with a service worker.
Maskable icons allow operating systems to crop the outer area. Important artwork must fit inside the central safe circle, which has a radius of 40% of the icon dimension. This tool produces a padded maskable PNG.
Yes. Import or paste JSON, modify the supported fields and export again. Unknown top-level fields are retained. Existing referenced icon files are not fetched or embedded; upload artwork to produce a complete icon ZIP.
No. Image decoding, validation, canvas exports, and ZIP creation happen locally in your browser. You are responsible for hosting the resulting files on your own website.
This will replace your current settings and artwork with a new starter project.
Create or edit a web app manifest, validate deployment-relative URLs and scope, design icons on canvas, and export manifest assets or a dependency-free ZIP.
Import a manifest with a custom metadata field, verify that the field remains, correct a start URL relative to the deployment path, then export and inspect the manifest and icon files together.
Field validation does not establish that a live site is installable. The builder does not create a service worker, caching strategy, fetch remote icons or deploy files. Imported external icon references remain until you explicitly replace them. The project stays in memory; only theme preference uses localStorage. HTTPS, MIME, CSP and real browser installation behavior need independent checks.
No. It creates manifest files but does not implement a service worker or verify deployment requirements.
No. External icon references are retained until you explicitly replace them.