> ## Documentation Index
> Fetch the complete documentation index at: https://docs.elementlabs.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Install a product

> Add the Element SDK and a product resource to your FiveM server.

## Outcome

The `element_sdk` resource and one product resource start cleanly on your server, with no warnings
for either.

## Prerequisites

* A server that meets the [server requirements](/getting-started/requirements), including any
  framework the product needs.
* The `element_sdk` archive and the product archive, downloaded from the CFX portal.
* Write access to `resources` and `server.cfg`.

## Steps

<Steps>
  <Step title="Extract the SDK" icon="download">
    ```text theme={null}
    resources/[element]/element_sdk/
    ```
  </Step>

  <Step title="Extract the product beside it" icon="folder-tree">
    ```text theme={null}
    resources/[element]/element_map/
    ```

    <Warning>
      Both directories must contain `fxmanifest.lua` at their top level. Archives often unpack into
      a folder of their own, leaving `element_map/element_map/fxmanifest.lua`. If that happens, move
      the inner directory up one level and delete the empty outer one. A resource nested one level
      too deep is invisible to the server.
    </Warning>

    <Note>
      The `[element]` folder is a convention that groups Element Labs resources together. Any
      location under `resources` works; the brackets tell FiveM to look inside for resources rather
      than to treat the folder as one.
    </Note>
  </Step>

  <Step title="Add both to server.cfg" icon="file-pen">
    The SDK goes first, and both go after the framework, inventory and database resources the
    product uses:

    ```cfg theme={null}
    ensure element_sdk
    ensure element_map
    ```
  </Step>

  <Step title="Restart the server" icon="arrows-rotate">
    A full restart, not a `refresh`. The product reads its configuration and matches your other
    resources at start.
  </Step>
</Steps>

## Verification

<Check>
  The console reports a clean start for both resources, with no `[ERROR]` or `[WARN ]` line naming
  either of them.
</Check>

Two lines mean the installation is not finished:

* A `[Dependencies]` error. The SDK is missing, stopped, or a version the product does not accept.
  See [SDK version requirements](/sdk/compatibility).
* A line reporting that no supported adapter was detected. A resource the product needs is not
  running. See [Supported server resources](/sdk/supported-resources).

If the product does not appear at all, work through [A product does not
start](/support/product-will-not-start).

## Next steps

* Some products need one further step to reach your other resources. See [Product
  integrations](/concepts/integrations). The product's own installation page says whether yours
  does.
* Change the product's behaviour through the files in its `configs` directory, described on that
  product's configuration pages. The rules that apply to all of them are in [Configuration
  files](/sdk/configuration).
* Keep a copy of everything you edit before you update. See [Update a product or the
  SDK](/getting-started/updating).