> For the complete documentation index, see [llms.txt](https://docs.overleaf.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.overleaf.com/troubleshooting-and-support/supported-browsers.md).
# Supported browsers
We support versions of the following browsers that have been released in the last 12 months:
* [Chrome](https://www.google.com/intl/en_uk/chrome/dr/download/?brand=SLLM\&ds_kid=43700079594422215\&gad_source=1\&gclid=CjwKCAjwgfm3BhBeEiwAFfxrG79f7C568qrxLsqjRZbdcdB0lDoSwjSs90ulx1ZSwZl1O4SaapNyMRoC8bgQAvD_BwE\&gclsrc=aw.ds)
* [Firefox](https://www.mozilla.org/en-GB/firefox/)
* [Safari](https://support.apple.com/en-gb/102665)
* [Microsoft Edge](https://support.microsoft.com/en-gb/topic/getting-the-latest-microsoft-edge-update-just-got-easier-5b65c03b-9059-4cfc-ae49-489574931f3b)
* [Firefox ESR](https://www.mozilla.org/en-GB/firefox/enterprise/)
We can’t guarantee support for beta or developer-preview browser versions. Please [get in touch](https://www.overleaf.com/contact) if you encounter any issues while using Overleaf with these.
If you're unable to upgrade to one of the supported browsers, we recommend accessing Overleaf from a different device that meets the requirements. Still, we would welcome it if you could [let us know](https://www.overleaf.com/contact) the details of your setup, as it helps us better understand our users' needs.
{% hint style="info" %}
Note that: there are some limitations when using Overleaf on a mobile device or tablet. If you’re using a supported browser and you’re still having issues, please see our [troubleshooting suggestions](/troubleshooting-and-support/resolving-pdf-rendering-and-project-loading-problems.md) for access, loading and display problems.
{% endhint %}
Seeing a blank PDF Viewer?
If you are using an older version of the browsers listed above, the PDF Viewer might appear completely blank. To solve this issue, you can swap your PDF Viewer setting to **Browser** (File> Settings> Editor). This does come with some [limitations](/navigating-in-the-editor/working-with-the-pdf-viewer/pdf-viewer-options-and-navigation.md#browser-pdf-viewer-limitations):
> * SyncTeX arrows [(jump-to-preview and jump-to-source)](https://learn.overleaf.com/learn/Kb/How_to_jump_to_the_source_code_from_the_typeset_PDF_\(SyncTeX\)) do not work.
> * Each **Recompile** will return to the first page of the output PDF.
> * Overleaf's PDF navigation controls are not available (only browser provided navigation tools are supported).
---
# 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.overleaf.com/troubleshooting-and-support/supported-browsers.md?ask=&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.
