# Supported environments

The current web shell needs WebGPU to start. Use HTTPS, or a local development
server on `localhost`, and a browser that can create a WebGPU adapter and device.
If that check fails, Lolly explains the requirement before opening a tool.

The web-only release approved on 9 October 2026 uses the completed Mac browser
checks below. These are results on **macOS 27, Apple M4**, with the browser's
default adapter and graphics settings. They do not establish support for the
same browsers on Windows, Linux, Android, iOS, Intel Macs or other GPUs.

## Qualification results

| Environment | WebGPU result | Versions and platform | Adapter and backend | Evidence |
|---|---|---|---|---|
| Chrome and Edge (Chromium) | Supported: tested on macOS only | Chrome 154.0.8037.99; Edge 155.0.4283.45; macOS 27, Apple M4 | Default Apple Metal 3 adapter; no software fallback | 9 October 2026; stock browsers, isolated headless hardware runs; required corpus passed, zero skips |
| Firefox | Supported: tested on macOS only | Firefox 157.0.1; macOS 27, Apple M4 | Default non-fallback adapter; GPU identity not reported by the browser | 9 October 2026; installed visible browser; required corpus passed |
| Safari (WebKit) | Supported: tested on macOS only | Safari 27.0.1; macOS 27, Apple M4 | Default Apple adapter; no software fallback | 9 October 2026; installed visible browser; required corpus passed |
| macOS app (WKWebView) | Supported: qualification build; native release held | WKWebView 22625.1.29.11.28; macOS 27, Apple M4 | Default Apple adapter; no software fallback | 9 October 2026; compiled qualification app, second execution with its existing isolated profile; startup, tool mount and required corpus passed |
| iOS and iPadOS app (WKWebView) | Pending: physical runtime not qualified | Not established | Not established | Archive compilation is recorded; device installation and runtime checks remain open |
| Windows app (WebView2) | Pending: physical runtime not qualified | Not established | Not established | Required device/runtime check has not run |
| Linux app (WebKitGTK) | Pending: physical runtime not qualified | Not established | Not established | Required device/runtime check has not run |
| Android app (WebView) | Pending: physical runtime not qualified | Not established | Not established | Required device/runtime check has not run |

The browser corpus checks numerical results on the main thread and in a worker,
photo baking, cancellation, device recovery and operation chains. Its browser
startup measurement covers the device service and tool mount fence, rather than
the complete gallery. The Mac qualification app also checked actual gallery
startup, a mounted tool, its embedded content and Content Security Policy.
These checks do not certify every presentation clicker, embedded website or
native platform.

## Release scope

Web artifacts can use the qualified browser rows without waiting for the
packaged apps. The signed web build, public web image and verified instance shell
select that scope explicitly. This approval leaves native releases held,
including the Mac package, until the full required matrix is published.

For a web artifact, run:

```bash
node scripts/webgpu-release-gate.ts --scope web
pnpm run check:release-checklist
pnpm run build:web:release
```

The signed build still requires the matching catalog signing key and public pin.
Qualification alone does not publish a build or deploy an instance.

`node scripts/webgpu-release-gate.ts` and `pnpm run check:release` keep the full
frontend gate. Tauri builds, native package workflows and the YunoHost release
command also keep that hold. A pending or missing result cannot pass the gate;
environment variables cannot bypass qualification. A tested unsupported result
may be recorded as **Not supported**, but an unrun check stays **Pending**.

The MCP, certificate service, Penpot service and documentation builds are
independent of this frontend matrix. Their release checks continue separately.

## Recorded evidence

The Chrome run used source commit
`20843cb22d3ad36dfd3d93e518bfd8ee812527a7`. The Firefox, Safari and Edge runs used
`26799926739fa58bbbf6a8e081f13ab5a8f74617`; the required browser corpus and launcher
inputs are unchanged between those commits. The Mac qualification app was built
from `ed6c32571593dba96b0562b47396ff42e2cf3270`; its passed execution is not a new
current-main build or a fresh-profile startup result. Original failed attempts
remain recorded separately.

Retained conformance reports have these SHA-256 digests:

| Report | SHA-256 |
|---|---|
| Chrome | `0c9e9628f215692b00f0eba5eacce1820c31d36dc47a57cef1190619bd66033f` |
| Edge | `9f04aac38b91bdf70a10f3078c288ebb690ad8d4827572f0810248fed2834a75` |
| Firefox conformance report | `bdc263c2268485ce9718d40feff26e993ebf68ebcdc30e55484172bbd9f62952` |
| Safari | `ea8b87aa0f60e763b6ac80b6d0663d83323e47ae8e899d2616ab1d4f28becdac` |
| Mac qualification app | `9f5ed9cd19f7f522a9a221141ace046b789b556b3085400ebb884c5c3bea7fec` |

For installation choices, see [Install Lolly](/info/install.html). For signed
artifact production, see the [Build Guide](/info/build-guide.html).

---

Code ([MPL 2.0](https://www.mozilla.org/en-US/MPL/2.0/)) · Content ([CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/)) · [lolly.tools](https://lolly.tools)