PWA Icon and Manifest Preflight — beta

Check a supplied web app manifest and icon files before a human/browser release review. This offline diagnostic helper returns a JSON report and visual icon preview sheets. It does not crawl your website, fetch URLs, certify installability, or replace browser testing.

Quick start

1. In Input, paste your manifest as raw JSON text (not an object).
2. Set manifestUrl and documentUrl to the manifest and page URLs. They are resolution contexts only; nothing is fetched.
3. Optionally supply icons, an array of objects containing src and strict base64 image bytes. Match src to a manifest icon reference. Do not include a data: prefix or a server file path.
4. Start one report with a maximum run cost of at least US$0.03. Open REPORT for findings and PREVIEW-00, etc., for images. The OUTPUT record is the final adapter result/index.

Minimal runnable example (intentionally has no supplied icon evidence):

{
  "manifest": "{\"name\":\"Example App\",\"short_name\":\"Example\",\"start_url\":\"/\",\"display\":\"standalone\",\"icons\":[]}",
  "manifestUrl": "https://example.test/manifest.webmanifest",
  "documentUrl": "https://example.test/",
  "icons": []
}

To get preview sheets, supply your own static PNG, JPEG or WebP icons as base64. Missing bytes are marked unverified, not evidence that a remote URL is broken. Use only material you are entitled to process, and do not submit secrets.

What is checked?

• Bounded, strict JSON and duplicate keys; manifest/icon declaration structure.
• Supplied image format, actual dimensions and MIME versus declarations.
• Icon purpose tokens (any, maskable, monochrome) and relevant warnings.
• Effective start URL, scope and ID/origin diagnostics using a conservative ASCII HTTP(S) URL subset.
• Original, circle, squircle and safe-zone-only icon previews for human visual review.

Manifest scope is a path prefix: /app also includes /application. If you intend a directory boundary, review /app/. Unsupported URL edge cases are not proof that a browser rejects those URLs.

The safe-zone illustration uses a centered circle with radius 40% of the smaller image dimension. It does not identify a logo or determine which pixels matter. Opaque pixels outside that circle do not prove logo clipping. Transparency is shown on a white example background; devices can differ.

Outputs

• REPORT: detailed JSON findings and severity counts.
• PREVIEW-00, etc.: PNG contact sheets for supplied supported icons.
• OUTPUT: final adapter result, report references and billing status.
• Dataset: one completion summary, useful for workflow integration. Its pending-not-authoritative billing field is not a payment ledger; consult the final OUTPUT and Apify's event accounting instead.

A completed report may contain errors. Treat error, warning, unverified and review findings according to your release policy; a successful Actor run does not mean a PWA passed browser installation checks.

Limits and exclusions

One manifest per run; 256 KiB manifest text; at most 10 icon declarations and 10 supplied assets; 4 MiB decoded file bytes per icon and 16 MiB combined; maximum side 2,048 pixels and 4,194,304 pixels per icon. The serialized adapter input is capped at 24 MiB; platform input limits may be lower.

Only static PNG/JPEG/WebP are supported. SVG, ICO, GIF and animated images are outside this beta's scope, not necessarily invalid browser icons. No remote fetching, service-worker audit, browser emulation, comprehensive WHATWG URL parsing, guaranteed issue detection, compliance score or installation certification is provided.

Pricing

US$0.03 per completed preflight report ($30 per 1,000), including reports with diagnostic error findings. Apify platform usage is included. There are no Actor-start or dataset-item event fees for this product. Structurally invalid input is rejected without a completed-report fee.

Each new run is a separate report. Interrupted or ambiguous write/charge states fail closed rather than promise exactly-once billing. Do not automatically retry ambiguous runs or clear/reuse their internal state; inspect the final result and platform event accounting first.

Beta verification and support

As of 26 October 2026, 106 local regression tests passed. Owner-only hosted synthetic tests verified report and preview artifacts, and one billing-enabled synthetic run completed with the intended event. These are development checks, not customer demand, earnings, certification or a production SLA. Maximum serialized payloads and full browser interoperability have not been validated in hosted testing.

For a reproducible issue, use this Actor's Apify Issues tab. Share a minimal synthetic example rather than private files or secrets. Visual review and real browser/device testing remain necessary.

References

• W3C Web Application Manifest
• Chrome maskable-icon guidance (Lighthouse PWA testing is deprecated; this Actor is not advertised as its replacement)
• Chrome DevTools PWA inspection