> ## Documentation Index
> Fetch the complete documentation index at: https://usefoil.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Browser compatibility

> Check Foil browser compatibility: supported Chrome, Edge, Firefox, and Safari versions, required APIs, and rollout guidance for webviews and embedded shells.

Foil targets current evergreen browsers. It is designed for modern browser runtimes that support JavaScript, WebAssembly, and the transport APIs required by the client bundle.

<Note>
  Compatibility means Foil can load and produce a server-verifiable result. It does not mean every browser exposes the same signal surface or behavioral fidelity. Chromium-family browsers currently have the strongest coverage.
</Note>

## Supported versions

| Browser                    | Minimum Version | Engine               |
| -------------------------- | --------------- | -------------------- |
| Chrome                     | 100+            | Chromium 100         |
| Microsoft Edge             | 105+            | Chromium 105         |
| Firefox                    | 115+            | Gecko (ESR baseline) |
| Desktop Safari             | 15.0+           | WebKit               |
| Mobile Safari / iPadOS     | 15.0+           | WebKit               |
| Android OS                 | 6.0+            | —                    |
| Chrome on Android          | 100+            | Chromium 100         |
| Samsung Internet           | 18.0+           | Chromium 105         |
| Brave                      | 1.37+           | Chromium 100         |
| Legacy browsers (IE, etc.) | —               | —                    |

## What Foil requires

In practice, Foil expects a modern browser with:

* JavaScript enabled
* WebAssembly support
* `TextEncoder` and `TextDecoder`
* Modern `fetch` support for API transport
* Event APIs used for interaction collection

Some probes and correlation features may work better when browsers also allow cookies, storage, and richer graphics or audio APIs, but those are not equally available on every engine.

## Rollout guidance

If your traffic mix includes Safari, Firefox, or mobile-heavy traffic:

1. Start in `report` mode.
2. Observe result distribution by browser family, using `latest_decision.verdict` on list responses or `decision.automation_status` on session-detail responses.
3. Validate real user flows on your highest-volume browsers and devices.
4. Enforce gradually, beginning with the highest-confidence automated sessions and the most abuse-sensitive endpoints.

## Embedded browsers and webviews

Foil can run in embedded contexts, but compatibility varies by host app and runtime. If you rely on:

* iOS webviews
* Android webviews
* in-app browsers
* Electron or other embedded shells

validate them explicitly before you depend on enforcement behavior.

## What's next

* [Browser SDK](/browser-sdk) — loading and initialization
* [Testing your integration](/testing) — simulate bot traffic across browsers
* [Going to production](/going-to-production) — rollout checklist