> For the complete documentation index, see [llms.txt](https://help.transform.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.transform.ai/getting-started/browser-compatibility.md).

# Browser Compatibility

### Overview

Transform requires a modern, supported web browser. Core features require JavaScript and cookies.

Use this page when diagnosing login, rendering, or permission prompts. Use [System Requirements](/getting-started/system-requirements.md) for device and network recommendations.

### Key Concepts

* **JavaScript**: required to render the app UI
* **Cookies**: required for session and preference storage
* **Site permissions**: microphone and notifications (optional, feature-dependent)
* **Extensions**: may interfere with scripts, cookies, or network requests

### How It’s Used

Use this checklist during rollout. Use it as the first step in browser-based troubleshooting.

### Benefits

* Fewer “page won’t load” issues
* More reliable sign-in sessions
* Cleaner audio capture when Meeting Notetaker is enabled

### Setup Steps

#### 1) Use a modern browser

Use an evergreen browser on the latest stable version. Update the browser regularly.

#### 2) Enable JavaScript

Confirm JavaScript is enabled for the Transform domain.

#### 3) Allow cookies

Confirm cookies are allowed for the Transform domain. Avoid strict cookie-blocking modes for primary usage.

#### 4) Allow pop-ups when required

Allow pop-ups for the Transform domain when a workflow opens a new window.

#### 5) Configure site permissions (feature-dependent)

* **Microphone**: required for Meeting Notetaker capture
* **Notifications**: optional for browser-level notifications

#### 6) Isolate extension-related issues

Test in a private browsing window to reduce extension impact. Disable extensions that block scripts or cookies when issues occur.

### Best Practices

* Standardize on one browser configuration across a delivery team.
* Avoid running heavy privacy or script-blocking extensions during delivery work.
* Use a dedicated browser profile for delivery work when policy allows.

### Summary

Browser compatibility depends on a modern browser, enabled JavaScript, allowed cookies, and correct site permissions. Isolate issues by testing without extensions and with a clean cache state.

Related:

* [System Requirements](/getting-started/system-requirements.md)
* [Login Problems](/troubleshooting/login-problems.md)
* [Getting Help](/troubleshooting/getting-help.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.transform.ai/getting-started/browser-compatibility.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.