> For the complete documentation index, see [llms.txt](https://docs.patcher.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.patcher.xyz/project/supported-platforms.md).

# Supported platforms

Patcher is a browser-based workspace. It runs anywhere a modern browser runs — no install, no local runtime.

## Desktop browsers

Patcher is developed against the current and previous major versions of modern evergreen desktop browsers:

* **Google Chrome**
* **Mozilla Firefox**
* **Apple Safari**
* **Microsoft Edge**

If you keep your browser up to date, Patcher should behave the same way on any of them.

### Safari

**Safari** is an explicitly supported target on both macOS and iPadOS. If you spot a bug that only reproduces on Safari, report it — Safari-only issues are treated the same as any other browser bug, not as edge cases.

## Mobile browsers

Patcher supports modern mobile browsers:

* **Safari on iOS and iPadOS**
* **Chrome on iOS and Android**

The mobile experience is optimized for browsing, reading, and light editing. Larger rack and patch editing sessions still work best on a desktop screen because of the space each canvas needs.

## Accessibility

Patcher aims to be usable without a pointing device.

* **Skip link** — a skip-to-content link is available near the top of the page so keyboard users can jump past navigation directly into the current view's main content.
* **Keyboard navigation** — the main interactive surfaces (module browsing, filters, rack and patch editing, user area, and account controls) are reachable and operable with keyboard input alone.
* **Focus visibility** — focused controls have a visible focus ring so it stays clear which element will receive the next keystroke.

If a control is not reachable with a keyboard, that is a bug worth reporting — see [Support and status](/project/support-and-status.md).

## Older or unsupported browsers

Older browser versions may still load Patcher but are not part of the supported set. If you hit visual or behavioral issues on an old browser, updating is usually the fastest fix.

## Related pages

* [Support and status](/project/support-and-status.md)
* [Contact us / Help / Community](/project/contact-us-help-community.md)
* [Account and privacy](/core-workflows/account-and-privacy.md)