Skip to content
TextArray1.41.0
100% local

Web app manifest generator

Build a valid manifest.json for your progressive web app from name, icons, colors and display options.

Output
Related tools
Meta tag generatorDeveloper tools
Humans.txt generatorDeveloper tools
Robots.txt generatorDeveloper tools
i18n key diffDeveloper tools
TOML to JSON converterDeveloper tools
SQL to JSONDeveloper tools
Web app manifest generator
A web app manifest tells browsers and operating systems how your progressive web app should look and behave when it's installed — its name, icon set, colors and whether it opens in its own window or a browser tab. This tool builds that manifest.json from a set of fields, so you don't have to remember the exact JSON shape or track down which keys are required.
Fill in the app name and short name, then set the display mode (standalone is the usual choice for an app that should feel native), orientation, and theme and background colors, which control the splash screen and browser chrome on Android. Add icons as one entry per line or separated by semicolons in the form src|sizes|purpose — for example /icon-512.png|512x512|any — and the tool fills in the MIME type from the file extension automatically. Shortcuts (jump-list entries like "Compose" or "Inbox") and related native-app links follow the same src|sizes|purpose-style shorthand, each field separated by a pipe.
The tool checks the fields as you type: it flags a missing app name before generating anything, and it warns — without blocking the output — when your icon set has no 192x192 or 512x512 entry, since installability checks on Android and desktop look for those specific sizes, or when an icon line left out its size altogether.
Everything runs locally in your browser; none of your app's details are sent anywhere. The output is the manifest.json content followed by the <link rel="manifest"> tag to paste into your page's <head>. Copy it, download it as a .txt file to rename yourself, or send it straight to another tool's input.
FAQ
Which fields does a manifest actually need?
Only a name (or short_name) is strictly required for this tool to generate anything. In practice, browsers also want at least a 192x192 and a 512x512 icon before they will offer to install the app — the tool warns if those are missing.
How do I format the icons field?
One icon per entry, separated by a semicolon or a new line, in the form src|sizes|purpose — for example /icon-192.png|192x192|any. Sizes and purpose are optional, but leaving out sizes triggers a warning.
What does prefer_related_applications do?
It tells the browser to suggest the native app listed under related applications instead of installing the web app. It only appears in the output once you add at least one related application.
Where do I save the generated file?
Save the JSON part as manifest.json at your site root (or wherever you prefer, adjusting the link href to match), and paste the generated <link> tag into your HTML <head>.
Is my app data uploaded anywhere?
No. The manifest is assembled entirely in your browser from the fields you fill in — nothing about your app is sent to a server.