TechnSols
Advertisement

Web Manifest Editor

Build a PWA web app manifest online free. Edit every field, validate install rules and download manifest.json. No install or sign-up.

Be the first to rate this tool

					

Fill in the app details, then press Validate Manifest to check and download manifest.json.

What Is Web Manifest Editor?

Web Manifest Editor is a free online tool by TechnSols that builds a web app manifest file for a progressive web app from a simple form. You fill in the app name, short name, start address, display mode, colours and icons, watch the JSON update live, press Validate Manifest to check it against the rules browsers apply, and download a finished manifest.json file.

Advertisement

A web app manifest is a small JSON file that tells a browser how a site should behave once a visitor installs it: the name on the home screen, the icon, the splash screen and address bar colours, and whether the app opens full screen like a native app or inside a browser window. Without a manifest, a browser never offers the install prompt, and a visitor who adds the site by hand gets a broken icon and a plain browser tab. Writing the JSON by hand means looking up every field name, and one missing comma stops the whole file from loading, with no visible error on the page. The editor removes that risk: the form builds the JSON for you, the preview shows exactly what will be saved, and the validator flags the problems that would block the install prompt. To check a manifest you already have, the PWA Manifest Inspector tool validates pasted manifest text only, while this editor builds and edits the file from a form.

Web Manifest Editor differs from the inspector: the inspector only checks a manifest you paste, while this editor creates and changes every field and downloads the result. Everything runs in your browser, and nothing is uploaded. The editor does not create icon artwork, write a service worker, or check a live site; the manifest file is the whole job, ready for the root of your site.

How To Use Web Manifest Editor?

Building a manifest takes two minutes, with no software to install and no account to make. The page opens with a working example filled in, so the first click shows a result.

Step 1: Fill In The App Details

Type the full app name and the short name that fits under the home screen icon, then add a short description, the start address and the scope. Pick the display mode and the orientation from the lists, and type the theme colour and the background colour as hex values. When the site also needs its sharing tags written, the Open Graph Generator tool builds the tags that control how a page looks when it is shared.

Step 2: Add The Icons And Watch The Preview

Add one icon per line in the icons box, with the file path, the size, the type, and an optional purpose such as maskable, for example /icons/icon-192.png 192×192 image/png maskable. The live preview updates with every keystroke. Browsers need at least one icon of 192 by 192 pixels and one of 512 by 512 pixels before they offer the install prompt, so list both sizes.

Step 3: Validate And Download The Manifest

Press Validate Manifest to run every check. The result list shows errors that must be fixed and warnings that could block the install prompt, with the fix for each one. When the checks pass, press Download to save manifest.json, upload it to your site root and link it from every page.

Why Use Web Manifest Editor?

A manifest looks simple, and that is why small mistakes in it are so costly. A missing icon size or a wrong display value silently stops the install prompt, and the site owner only finds out when nobody installs the app.

Install Prompts Have Strict Rules

Chrome will not offer the install prompt unless the manifest has a name, a short name, a start address, a display mode of fullscreen, standalone or minimal user interface, and icons that include at least one 192 by 192 entry and one 512 by 512 entry. A manifest that misses any one of these looks fine in a text editor and fails silently in the browser. The editor checks every rule and names the missing piece, so the prompt works the first time the file goes live. The full field list is covered in the MDN manifest guide, which documents each member.

Hand Written JSON Breaks Easily

A manifest is JSON, so a trailing comma, a missing quote or a wrong bracket makes the whole file unreadable, and the browser gives no error message to explain why. The editor builds the JSON from the form, so the syntax is always correct, and the live preview shows the exact text that will be saved. When a manifest file needs its JSON checked on its own, the JSON Formatter tool formats and checks pasted JSON.

Colours And Display Shape The First Impression

The theme colour paints the address bar and browser chrome around the app, and the background colour fills the splash screen while the app loads. A theme colour that clashes with the app, or a background colour that flashes white on a dark app, makes the install feel broken. The editor keeps both colours in the form where they can be tried and changed.

What Can You Do With Web Manifest Editor?

The editor fits anywhere a site is turning into an installable app, from a first manifest for a new site to a quick fix for an app that never shows the install prompt.

Turn A Website Into An Installable App

A shop, a news site or a tool site can offer an app like install without building a native app at all. Fill in the name, the start address and the icons, download the file, upload it to the site root, and add the link tag to every page. Visitors on Android then see the install prompt, and the app opens from the home screen with its own icon and no browser chrome. For the pages the app opens, the HTML Element Inspector tool shows the live markup of each page so its tags and structure can be checked.

Fix An App That Never Shows The Prompt

When an app never shows the install prompt, the manifest is the first suspect, and the fastest to check. Copy the current values into the form, then validate. A missing 512 icon, a short name over twelve characters, or a start address outside the scope each shows up as a named warning, and fixing the named problem is a one line change instead of a day of guessing. When the start address itself needs checking, the Link Anchor Checker tool checks every link on the start page and reports the broken ones.

Keep One Manifest For Every Page

A site with many pages needs one manifest, linked from every page, not one per page. The editor builds that single file, and the scope field says which pages belong to the app, so a page outside the scope never opens inside the installed app by mistake. Save the downloaded file, and edit it in the form again whenever the name, the colours or the icons change.

Quality And Settings

The editor has no quality setting to tune, because a manifest is a data file rather than a matter of taste. The settings that matter are the name, the start address, the display mode, the colours and the icons. A value the editor cannot use is reported with the fix, never guessed at.

Advertisement
  • Name and short name are both required, and the short name warns when it runs past twelve characters.
  • Start address and scope are checked together, and a start address outside the scope is flagged before the file is saved.
  • Display offers fullscreen, standalone, minimal user interface and browser, and orientation offers any, natural, landscape and portrait.
  • Theme colour and background colour must be hex values such as #2563eb or #ffffff, and anything else is reported as an error.
  • Icon lines take a file path, a size such as 192×192 and a type, and missing 192 or 512 sizes are flagged as warnings.

When a field fails validation, the message names the field and says what a valid value looks like. The editor builds the manifest you describe, and only the live site can show whether the icon files it points to actually exist.

How Web Manifest Editor Works?

The editor reads the form and builds a manifest object in memory: name, short name, description, start address, scope, display, orientation, theme colour, background colour and the icons list. The live preview shows that object as pretty printed JSON, and it updates on every keystroke, so the text you see is always the text that will be saved.

Validation runs the checks browsers apply before they offer an install prompt. It requires a name, a short name and a start address, checks the display and orientation values against the allowed lists, checks both colours are hex values, and checks the icons for the 192 and 512 sizes Chrome requires. A missing required field is an error, and a missing install size is a warning, because the file is still valid JSON but the prompt will not appear. The guide at web.dev PWA guide explains the same install rules. When the manifest is live and the page markup needs checking too, the CSS Selector Tester tool shows which elements a selector matches on the page that links to it, and the HTML Entity Encoder tool encodes special characters in page text so they display correctly.

Privacy

Web Manifest Editor runs entirely in the browser. The app name, the addresses and the icon paths that are typed never leave the device, and nothing is uploaded to a server or stored anywhere. There is no account and no tracking. When the same project also needs pasted data checked, the JSON Validator tool works the same way, with everything running locally and nothing sent away.

Because nothing is stored, there is nothing to delete and nothing to export. The downloaded manifest.json file is the only record.

Tips

A few habits make web app manifests much easier to ship.

  • Keep the short name to twelve characters or fewer, because a longer name is cut off.
  • Use standalone display for most apps, since it hides the browser chrome and makes the app feel native.
  • Serve the manifest over HTTPS, because install prompts never appear on plain HTTP sites.
  • Link the manifest from every page with the same link tag, so the browser finds it on any page.
  • Test the install prompt on a real Android device after publishing, because desktop browsers do not show the same prompt.

When the app also needs to work offline, add a service worker as a separate step, because the manifest alone does not cache anything. For a full check of the site after the manifest goes live, the Website Resource Size Analyzer tool measures every resource the app pages load and reports what still needs fixing.

More Tools For The Same Job

The tools below solve the jobs that sit next to a web app manifest in the same PWA project.

  • PWA Manifest Inspector: validates a manifest you paste, and reports errors and warnings.
  • Meta Tag Generator: builds the meta tags that describe each page to browsers and search engines.
  • Open Graph Generator: builds the sharing tags that control how a page looks when it is shared.
  • JSON Formatter: formats and checks pasted JSON.
  • JSON Validator: checks whether pasted JSON is valid and points at the exact syntax error.
  • HTML Validator: checks the markup of the page that links to the manifest.
  • URL Encoder: encodes special characters in an address so links work as intended.
  • Canonical URL Checker: reads the canonical tag on a live page.
  • SEO Audit Tool: scans the pages that matter and reports the SEO problems.
  • Robots.txt Generator: builds a robots.txt file for your site.

FAQ

The questions below cover the points that come up most often when a web app manifest is built for the first time.

What Is A Web App Manifest?

A web app manifest is a JSON file, usually named manifest.json, that describes how a web app should look and behave when it is installed on a device. It sets the app name, the short name, the icons, the colours, the start address and the display mode.

Why Does My App Not Show The Install Prompt?

Chrome needs a name, a short name, a start address, a display mode of fullscreen, standalone or minimal user interface, and icons of at least 192 by 192 and 512 by 512 pixels. It also needs HTTPS and a service worker. Run the editor and fix the named problem first.

Where Do I Put The Manifest On My Site?

Put manifest.json at the root of your site, next to the home page, and link it from every page with a link tag. Browsers fetch it from that address, so a file in a subfolder works too, as long as the link tag points at it and the scope covers the pages.

Do I Need A Service Worker Too?

Yes, for the install prompt and for offline use. The manifest describes the app, and the service worker caches the files and handles offline requests. The editor builds the manifest only, so write the service worker as a separate step.

Is Web Manifest Editor By TechnSols Free?

Yes, Web Manifest Editor by TechnSols is completely free to use online, with no sign up, no install and no limit on the number of manifests. It runs in the browser, nothing is uploaded, and the manifest.json file downloads free too.

A manifest stops being a puzzle once the install rules are known. Fill in the form, watch the preview, fix the warnings, and download a manifest browsers accept the first time.

Follow TechnSols on Google
Add TechnSols as a preferred source to see more of our tools in Google Search.
Add to Preferred Sources
Advertisement