> For the complete documentation index, see [llms.txt](https://docs.noctrastore.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.noctrastore.net/noctra-garage/overview.md).

# Overview

A flexible garage system for owned vehicles, shared fleets, impounds, and custom locations.

Noctra Garage provides a complete vehicle storage experience with an in-game garage creator, immersive vehicle previews, configurable access rules, and optional vehicle persistence.

It supports **ESX**, **QBCore**, **Qbox**, and custom frameworks. Garages can be created for road vehicles, boats, or planes.

## Main features

* Create and edit garages without manually writing location tables.
* Store vehicle properties, upgrades, fuel, damage, and deformation.
* Configure multiple storage and spawn points for each garage.
* Restrict access by job, gang, grade, or garage ownership.
* Add storage, retrieval, transfer, and impound fees.
* Use standard garage previews, custom-map showrooms, or built-in IPL showrooms.
* Let players favorite vehicles, add tags, and transfer supported vehicles.
* Sell garages to players, share access keys, and transfer garage ownership.
* Keep retrieved vehicles persistent across restarts when persistence is enabled.
* Integrate with common fuel, vehicle-key, text UI, and target resources.

## Garage types

| Type           | Purpose                                                                                             |
| -------------- | --------------------------------------------------------------------------------------------------- |
| **Owned**      | Shows vehicles belonging to the player. This is the standard choice for public and private garages. |
| **Shared**     | Provides one shared vehicle pool for players who can access the garage.                             |
| **Predefined** | Offers a configured fleet with optional vehicle limits and reset rules.                             |
| **Impound**    | Holds impounded vehicles and supports release fees or release to another garage.                    |

Access rules and the storage restriction are separate settings. A garage can, for example, be limited to a police job while still accepting only vehicles owned by the player.

## Where to begin

Install the resource and database first, then use the garage creator to build your locations.

{% content-ref url="/pages/FSAZJXTDb13aIsixLteb" %}
[Installation](/noctra-garage/installation.md)
{% endcontent-ref %}

{% content-ref url="/pages/qHyzDGEz2oU1BFy8XB7i" %}
[Garage creator](/noctra-garage/garage-creator.md)
{% endcontent-ref %}


---

# 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.noctrastore.net/noctra-garage/overview.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.