> For the complete documentation index, see [llms.txt](https://studioworks.gitbook.io/studioworks-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://studioworks.gitbook.io/studioworks-docs/installation/quickstart.md).

# Quickstart

From purchase to a working asset on your FiveM server.

You need access to your server files and server console. Use a test server for the first installation where possible.

{% stepper %}
{% step %}

### Download and read the instructions

Use the delivery link in your purchase confirmation. For Cfx.re-delivered assets, use the matching account in the [Cfx.re Portal](https://portal.cfx.re/). Check the product instructions for its framework, inventory, server requirements, and additional resources.
{% endstep %}

{% step %}

### Create a backup

Back up the affected files and server configuration. If the product requires database changes, back up the relevant data as well. Keep an untouched copy of the original package.
{% endstep %}

{% step %}

### Extract the complete resource

Copy the actual resource folder into `resources`. The included `fxmanifest.lua` should be directly inside that folder. A double wrapper such as `product/product/fxmanifest.lua` is a common installation mistake.
{% endstep %}

{% step %}

### Start dependencies, then the asset

Add the required resources to your server configuration in the documented order. Use the real resource folder name. See [Starting resources](/studioworks-docs/installation/starting-resources.md) for an example.
{% endstep %}

{% step %}

### Test the basic feature

Read the server console first, then reconnect your client and test the documented feature. For vehicles and peds, use the specified model name in an existing, authorized spawn tool. There is no universal spawn chat command for every server.
{% endstep %}
{% endstepper %}

## Installation checklist

* The resource starts without an error.
* The model or core script feature works in the intended test.
* It still loads after a server restart.
* Only then do you connect additional garages, inventories, or administration systems.

If a step fails, use [Troubleshooting](/studioworks-docs/troubleshooting.md). A failed integration test does not automatically mean the asset files are broken.

***

[StudioWorks Store](https://tebex.studio-works.net/) · [Discord & Support](https://discord.gg/UmqU67rp4v)


---

# 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://studioworks.gitbook.io/studioworks-docs/installation/quickstart.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.