Skip to content

Manifest member in Manifest

start_url manifest member

Published Updated

Limited availabilityNot supported in Firefox (Desktop)W3C

The start_url manifest member sets the URL an installed app opens when the user taps its icon. Use it to choose a launch page independently of the page open at installation. It is resolved against the manifest URL, must share the origin of the document that links the manifest, and a declared scope that does not contain it is ignored; it is also the fallback source of the app’s identity when id is absent.

Engines with an install path read it: Chrome 39, Edge 79, Samsung Internet 4.0, Firefox 79 on Android, Safari 11.3 on iOS and 17 on macOS (BCD manifests.webapp.start_url). Chromium additionally treats a valid start_url as an installability requirement.

Property Value
Type string, parsed as a URL relative to the manifest URL.
Default the URL of the document that linked the manifest. Chromium also falls back to that document URL after dropping a cross-origin value with property 'start_url' ignored, should be same origin as document. (manifest_parser.cc).
Example value "/app/?utm_source=homescreen".

If start_url is not within the declared scope, Chromium keeps start_url and drops scope instead, logging property 'scope' ignored. Start url should be within scope of scope URL., so the app silently receives the default scope (the start URL with its filename, query, and fragment removed). And because the processed id defaults to start_url without its fragment (the query stays), changing the path of start_url on an app without an id gives the manifest a different identity, which the browser treats as a new PWA rather than an update of the installed one (Chrome for Developers, “Uniquely identify PWAs with the web app manifest id property”).

The launch URL provides a default entry. Notification clicks, shortcuts, share_target, and file_handlers can open other in-scope URLs, so each of those routes should also work as a cold start.

The examples use one manifest served from https://app.example/manifest.webmanifest.

Relative and absolute forms that resolve to the same launch page

Section titled “Relative and absolute forms that resolve to the same launch page”

Relative values resolve against the manifest URL, not against the page that linked it. A manifest at /manifest.webmanifest with "start_url": "app/" therefore launches https://app.example/app/, the same as the absolute form.

{
"start_url": "app/",
"scope": "/app/"
}

The absolute form "https://app.example/app/" is equivalent; a value on another origin such as "https://cdn.example/app/" is discarded and the document URL takes its place.

Tagging launches for analytics and reading the tag at startup

Section titled “Tagging launches for analytics and reading the tag at startup”

A query string on start_url is a simple way to tell an installed-app launch from a browser visit without a dedicated API, although anyone can also open the tagged URL in a tab. The script reads the parameter once, reports it, and removes it from the address so a reload or a copied link does not count as another launch; when the parameter is missing nothing is sent.

{
"start_url": "/app/?utm_source=homescreen&utm_medium=pwa"
}
const params = new URLSearchParams(location.search);
if (params.get('utm_source') === 'homescreen') {
navigator.sendBeacon('/analytics', JSON.stringify({ launch: 'installed-app' }));
params.delete('utm_source');
params.delete('utm_medium');
history.replaceState(history.state, '', `${location.pathname}${params.size ? `?${params}` : ''}`);
}

A changed start_url, query string included, is one of the differences that makes Chrome queue a manifest update (web.dev, “How Chrome handles updates to the web app manifest”). The check runs at launch when the manifest has not been checked in 24 hours, desktop Chrome installs the update after all the app’s windows close, and a changed start_url there requires id to be set.

Moving the launch page without creating a second install

Section titled “Moving the launch page without creating a second install”

Before changing start_url on a shipped app, pin id to the value the browser already derived, which DevTools shows as the Computed App Id (the old start_url without its fragment, query included). With id present, the new start_url is applied as an update; without it, Chromium treats the manifest as a different app. Here the old start_url was /app/.

{
"id": "/app/",
"start_url": "/app/home/?utm_source=homescreen",
"scope": "/app/"
}

Once id is set, start_url can change as long as its origin stays the same (Chrome for Developers).

Specifications

SpecificationStatus
Web App Manifest: start_urlW3C
  • Legend
  • Yes
  • Partial
  • Flag
  • No
  • Unknown
Browser / PlatformSupportVersionsConfidenceSourceNotes
Chrome (Desktop)#Yes39highsource1
Chrome (Android)#Yes39highsource23
Edge (Desktop)#Yes79highsource45
Firefox (Desktop)#No—highsource6
Firefox (Android)#Yes79highsource—
Safari (macOS)#Yes17highsource—
Safari (iOS)#Yes11.3highsource—
Samsung Internet#Yes4.0highsource78
WebView (Android)#Yes39highsource910
  1. `start_url` is required for a web app to be installable.
  2. `start_url` is required for a web app to be installable.
  3. Derived by browser-compat-data mirroring from Chrome.
  4. `start_url` is required for a web app to be installable.
  5. Derived by browser-compat-data mirroring from Chrome.
  6. No Firefox support is recorded in browser-compat-data.
  7. `start_url` is required for a web app to be installable.
  8. Derived by browser-compat-data mirroring from Chrome Android.
  9. `start_url` is required for a web app to be installable.
  10. Derived by browser-compat-data mirroring from Chrome Android.

Source data: /compatibility/manifest-start-url.json · Global usage: 94 % (StatCounter 2026-09, CC BY-SA 4.0)

Source: spec · MDN · Last verified 2026-10-03 · Confidence: high (computed from sources)