> For the complete documentation index, see [llms.txt](https://docs.roomle.com/rubens/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roomle.com/rubens/quick-start-guides/switch-browser-gpu-on-windows.md).

# Switch Browser GPU on Windows

## 1. Open the Windows Graphics Settings

* Click on the Windows Start menu
* Search for "Graphics Settings" and open it

![browser-graphics-settings-1.png](https://2782441740-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjLjPj3wCHnfCfuOYQpf4%2Fuploads%2Fgit-blob-3fb65bc98ecdb12e18b43982ceb66853838f0b90%2Fbrowser-graphics-settings-1.png?alt=media)

## 2. Add your browser to the list

* In the Graphics Settings window, under "Customized settings for application"
* If your browser is not listed, click on the "Add desktop app" button to add it ![browser-graphics-settings-2.png](https://2782441740-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjLjPj3wCHnfCfuOYQpf4%2Fuploads%2Fgit-blob-147bf92e86f2469147a58063192196a03a284e14%2Fbrowser-graphics-settings-2.png?alt=media)
* Click on the "Browse" button and navigate to the installation folder of your browser (e.g., Chrome, Edge, Firefox)
  * For chrome this is usually located at `C:\Program Files\Google\Chrome\Application\chrome.exe`
  * For edge this is usually located at `C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe`
  * For firefox this is usually located at `C:\Program Files\Mozilla Firefox\firefox.exe`
* Select the browser executable file (e.g., `chrome.exe`, `msedge.exe`, `firefox.exe`) and click "Add" ![browser-graphics-settings-3.png](https://2782441740-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjLjPj3wCHnfCfuOYQpf4%2Fuploads%2Fgit-blob-5d17ee9bde45b5dcdaecd0354976eb597d363583%2Fbrowser-graphics-settings-3.png?alt=media)
* The browser will now appear in the list of apps with graphics preferences

## 3. Set the GPU preference for your browser

* Click on the browser entry in the list and then open the dropdown menu
* In the "GPU preference" dropdown, explicitly select your "High performance" device ![browser-graphics-settings-4.png](https://2782441740-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjLjPj3wCHnfCfuOYQpf4%2Fuploads%2Fgit-blob-42f1852978a12fbb5a528d81a370463124b1869b%2Fbrowser-graphics-settings-4.png?alt=media)
* If you want this to apply to all of your browsers, repeat the steps for each browser you want to configure

## 4. Restart your browser

* Close all instances of your browser and reopen it to ensure the changes take effect
* The warning about the integrated GPU should no longer appear, and your browser should now be using the dedicated GPU for better performance


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.roomle.com/rubens/quick-start-guides/switch-browser-gpu-on-windows.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
