> For the complete documentation index, see [llms.txt](https://wiki.retrobat.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.retrobat.org/systems-and-emulators/supported-game-systems/game-consoles/atari-consoles/jaguar.md).

# Jaguar

Atari

<div align="left"><figure><img src="https://raw.githubusercontent.com/fabricecaruso/es-theme-carbon/52ff37c9e265587d006945a2ba695b5a962b3a3d/art/logos/atarijaguar.svg" alt=""><figcaption></figcaption></figure></div>

Game Console - Lifespan: 1993 - 1996

{% embed url="<https://en.wikipedia.org/wiki/Atari_Jaguar>" %}

## Information

<table data-header-hidden><thead><tr><th width="184"></th><th></th><th data-hidden></th></tr></thead><tbody><tr><td><strong>Emulators</strong></td><td><ul><li>libretro: virtualjaguar</li><li>BigPEmu</li><li>bizhawk</li><li>phoenix</li></ul></td><td></td></tr><tr><td><strong>Games Location</strong></td><td><span data-gb-custom-inline data-tag="emoji" data-code="1f4c1">📁</span> roms \ <span data-gb-custom-inline data-tag="emoji" data-code="1f4c2">📂</span> jaguar</td><td></td></tr><tr><td><strong>File extensions</strong></td><td>.zip .7z .cue .cdi .j64 .jag .rom .abs .cof .bin .prg .squashfs</td><td></td></tr></tbody></table>

## System Features

<table><thead><tr><th width="245">Retroachievements</th><th width="200">Netplay</th><th>Controller autoconfig</th></tr></thead><tbody><tr><td>lr-virtualjaguar: YES<br>BigPEmu: NO<br>Bizhawk: YES<br>Phoenix: NO</td><td>lr-virtualjaguar: NO<br>BigPEmu: NO<br>Bizhawk: NO<br>Phoenix: NO</td><td>lr-virtualjaguar: YES<br>BigPEmu: YES<br>Bizhawk: YES<br>Phoenix: YES</td></tr></tbody></table>

## BIOS

<table><thead><tr><th width="284">Bios file</th><th width="111.03610108303252">Folder</th><th>md5</th></tr></thead><tbody><tr><td>[BIOS] Atari Jaguar (World).j64</td><td><code>\bios</code></td><td>cb492f093cd9e22a913d158741e8f00a</td></tr></tbody></table>

## Controls

### VirtualJaguar, Bizhawk and Phoenix

<div align="left"><figure><img src="https://github.com/RetroBat-Official/retrobat-tattoos/blob/main/default/jaguar.png?raw=true" alt=""><figcaption></figcaption></figure></div>

### BigPEmu

<div align="left"><figure><img src="https://github.com/RetroBat-Official/retrobat-tattoos/blob/main/default/jaguar_bigpemu.png?raw=true" alt=""><figcaption></figcaption></figure></div>

## Specific system information

There is no specific System information documented here yet.

{% hint style="warning" %}
You need to use the ***Configure BigPEmu.bat*** file to run BigPEmu or run it from within RetroBat for the configuration to be correctly saved.

All configuration done by launching directly ***BigPEmu.exe*** will be ignored by RetroBat.
{% endhint %}


---

# 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://wiki.retrobat.org/systems-and-emulators/supported-game-systems/game-consoles/atari-consoles/jaguar.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.