FiveM Native Database Search

Search 200+ common FiveM natives by name, hash, or category. Get parameters, return types, descriptions, and Lua examples.

What this tool is for

FiveM exposes thousands of game natives, and their names describe the engine rather than the task, so finding the right one usually means knowing it already. This search is limited to the natives that actually come up in server development, grouped by area, with parameters, return type and a usage example next to each entry.

How to use it

  1. Step 1:

    Search by name if you know it, or browse the category that matches your task, for example vehicles or peds.

  2. Step 2:

    Read the parameters. The order matters and there are no named arguments in Lua.

  3. Step 3:

    Check the return type. Many natives return a handle you have to keep in order to change the entity later.

  4. Step 4:

    Copy the example and adapt it, rather than writing the call from memory.

Frequently asked questions

What is the difference between client and server natives?

Most game natives only exist on the client, because only the client renders the world. The server has a much smaller set around players, entities and identifiers. A client native called on the server simply does not exist and throws.

Why does a native return nothing?

Usually the entity does not exist yet or is not owned by this client. Models need RequestModel and a wait for HasModelLoaded, and entity natives return zero for anything outside the player scope.

Can I call natives by hash?

Yes, Citizen.InvokeNative with the hash works and is sometimes the only option for natives without a Lua wrapper. It is harder to read, so prefer the named form wherever one exists.

How do I know whether a native is expensive?

Every native call crosses from Lua into the game engine, so the cost is in the number of calls, not the individual one. A native inside a 0 ms loop runs sixty times a second. Cache results that do not change per frame.