> 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/support/purchase-download-faq.md).

# Purchase & download FAQ

Answers about purchase accounts, delivery, updates, and requirements.

## Where can I buy StudioWorks products?

Use the [official StudioWorks Tebex Store](https://tebex.studio-works.net/). Check the individual product listing for included features and requirements.

## Where is my download?

Follow the delivery instructions in your purchase confirmation. For Cfx.re-delivered assets, check the account used for the purchase in the [Cfx.re Portal](https://portal.cfx.re/). Delivery methods can differ between products.

## I paid, but cannot find the download

Check payment status, email address, and spam folder. Compare the Cfx.re account you are using with the one used at checkout. If delivery is still unclear, send the product name and order reference privately to support. Do not buy again as a troubleshooting step.

## I used the wrong account

Contact support with your order reference. Account or asset transfers depend on the platform's available options; these docs do not promise an automatic transfer. Check all your assets before changing server keys.

## Does every product support ESX, QBCore, Qbox, or standalone?

The individual product listing defines support. Loading a model and integrating it with a shop or inventory are separate tasks. Ask before buying if your combination is not listed.

## Can I rename the resource?

Only if the product instructions allow it. Resource names, exports, and integrations can depend on each other. Keep the original name for the first test.

## How do I get updates?

Use the delivery/update method provided for that product. Follow [Updates & backups](/studioworks-docs/installation/updates-backups.md) to preserve your settings while incorporating new configuration fields.

## Can I edit protected files?

Use only the configuration and integration files explicitly intended for customization. Leave protected files unchanged. For protected-file errors, see [Escrow & licensing](/studioworks-docs/troubleshooting/escrow-licensing.md).

## Which rules apply to usage, refunds, and redistribution?

The terms and product information shown in the store or checkout apply. For a specific order, use private support. These technical guides do not add purchase conditions.

***

[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/support/purchase-download-faq.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.
