Skip to content

Black Friday: 20% off until Nov 30Server packs

RPScripts

FiveM Markers: Marker Types and How to Use DrawMarker

By Luke, RPScripts

On this page

A FiveM marker is a 3D shape drawn in the game world with the DrawMarker native, such as the cylinder that shows where to stand to open a garage or a shop. Markers have no handle and do not stay on screen by themselves: a client script has to draw them again on every frame.

The marker type IDs below were copied from the official FiveM markers reference on 16 November 2026. Parameters come from the DrawMarker entry in the natives reference.

What is a marker in FiveM?

Markers mark interaction points in the world: a duty point in a police station, a garage entrance, a job pickup. They are purely visual. Pressing a key at a marker, opening a menu or teleporting the player is separate code you write around it, usually with a distance check.

A marker is not a blip. A blip is an icon on the map and the minimap, created once and kept by handle; the FiveM blips reference covers sprite and color IDs for those. Many locations use both: a blip so players find the place, and a marker so they know where to stand.

The markers on this page are fixed points defined in code. Markers that players place themselves from a menu are a different feature, which a ping marker script for FiveM provides.

FiveM marker types

The first argument of DrawMarker is the marker type. The reference lists 44 types, 0 to 43. The names are given exactly as the reference spells them; types 41 and 43 have no name there, only a question mark.

IDMarker name
0MarkerTypeUpsideDownCone
1MarkerTypeVerticalCylinder
2MarkerTypeThickChevronUp
3MarkerTypeThinChevronUp
4MarkerTypeCheckeredFlagRect
5MarkerTypeCheckeredFlagCircle
6MarkerTypeVerticleCircle
7MarkerTypePlaneModel
8MarkerTypeLostMCTransparent
9MarkerTypeLostMC
10MarkerTypeNumber0
11MarkerTypeNumber1
12MarkerTypeNumber2
13MarkerTypeNumber3
14MarkerTypeNumber4
15MarkerTypeNumber5
16MarkerTypeNumber6
17MarkerTypeNumber7
18MarkerTypeNumber8
19MarkerTypeNumber9
20MarkerTypeChevronUpx1
21MarkerTypeChevronUpx2
22MarkerTypeChevronUpx3
23MarkerTypeHorizontalCircleFat
24MarkerTypeReplayIcon
25MarkerTypeHorizontalCircleSkinny
26MarkerTypeHorizontalCircleSkinny_Arrow
27MarkerTypeHorizontalSplitArrowCircle
28MarkerTypeDebugSphere
29MarkerTypeDollarSign
30MarkerTypeHorizontalBars
31MarkerTypeWolfHead
32MarkerTypeQuestionMark
33MarkerTypePlaneSymbol
34MarkerTypeHelicopterSymbol
35MarkerTypeBoatSymbol
36MarkerTypeCarSymbol
37MarkerTypeMotorcycleSymbol
38MarkerTypeBikeSymbol
39MarkerTypeTruckSymbol
40MarkerTypeParachuteSymbol
41?
42MarkerTypeSawbladeSymbol
43?

The reference page shows an image of each type, which is the quickest way to choose one.

DrawMarker parameters

DrawMarker takes 24 arguments in this order. Descriptions are condensed from the natives reference.

#ParameterTypeWhat it does
1typeintMarker type ID from the table above.
2–4posX, posY, posZfloatWorld position to draw the marker at.
5–7dirX, dirY, dirZfloatDirection vector; 0.0 for all three uses the rotation values instead.
8–10rotX, rotY, rotZfloatRotation, only used when the direction vector is 0.0.
11–13scaleX, scaleY, scaleZfloatSize on each axis.
14–17red, green, blue, alphaintColor and transparency, each 0–255.
18bobUpAndDownBOOLSlowly animates the marker up and down.
19faceCameraBOOLTurns the marker into a billboard that always faces the camera.
20p19intTypically set to 2; the reference says it does not seem to matter directly.
21rotateBOOLRotations only apply to the heading.
22textureDictchar*Texture dictionary to draw the marker with, or nil.
23textureNamechar*Texture name inside that dictionary, or nil.
24drawOnEntsBOOLWhether the marker draws on intersecting entities.

Pass the type as a number. Positions, directions, rotations and scales are floats, so write 1.0, not 1, as the native examples do.

How do you draw a marker in FiveM?

The reference states that DrawMarker "has to be called every frame", for example in a Wait(0) loop. A marker drawn once shows for a single frame and is gone. A minimal client script:

-- client.lua
local point = vector3(0.0, 0.0, 0.0) -- replace with your location

CreateThread(function()
    while true do
        Wait(0)
        DrawMarker(1, point.x, point.y, point.z - 1.0,
            0.0, 0.0, 0.0,      -- direction
            0.0, 0.0, 0.0,      -- rotation
            1.5, 1.5, 1.0,      -- scale
            0, 150, 255, 120,   -- red, green, blue, alpha
            false, false, 2, false, nil, nil, false)
    end
end)

This draws the marker, but it runs the draw on every frame for every player, wherever they are on the map. The next pattern fixes that.

Drawing markers only when the player is near

Check the distance first and only enter the per-frame branch close to the point. Far away, the loop sleeps longer:

-- client.lua
local point = vector3(0.0, 0.0, 0.0) -- replace with your location
local drawDistance = 20.0
local useDistance = 1.5

CreateThread(function()
    while true do
        local sleep = 1000
        local playerCoords = GetEntityCoords(PlayerPedId())
        local distance = #(playerCoords - point)

        if distance < drawDistance then
            sleep = 0
            DrawMarker(1, point.x, point.y, point.z - 1.0,
                0.0, 0.0, 0.0, 0.0, 0.0, 0.0,
                1.5, 1.5, 1.0,
                0, 150, 255, 120,
                false, false, 2, false, nil, nil, false)

            if distance < useDistance and IsControlJustReleased(0, 38) then
                -- E was released while standing in the marker
                TriggerEvent('my_resource:openMenu')
            end
        end

        Wait(sleep)
    end
end)
  • #(playerCoords - point) is the distance between two vectors. The FiveM docs use the same form in their own examples.
  • Control 38 is INPUT_PICKUP, the E key on keyboard, according to the FiveM controls reference. Check it inside the per-frame branch, because a "just released" check needs to run on the frame the key goes up.
  • my_resource:openMenu is a placeholder for your own event or function.

The values 20.0, 1.5 and 1000 are starting points, not documented limits. Tune them to the location.

Why markers cost performance

The FiveM docs describe scripts as cooperatively multitasked: a loop has to give the game time with Wait, and a loop with Wait(0) runs again on the next frame. One marker loop is cheap; dozens of them, each running every frame for every location on the map, add up. Three habits keep it in check:

  • Sleep for longer while the player is far from every marker, as in the example above.
  • Use one thread that loops over a table of locations instead of one thread per marker.
  • Measure before and after a change instead of guessing.

The guide to optimizing FiveM server performance explains how to measure resource cost with resmon and the profiler. These habits follow from the every-frame rule; we did not benchmark the examples on this page.

Markers and checkpoints

Checkpoints are a different system. They are created once with CreateCheckpoint, which returns a handle; its reference entry warns that the game already handles checkpoints, so you must not loop them like markers. They use their own type IDs listed in the FiveM checkpoints reference. Do not pass a checkpoint ID to DrawMarker or the other way round.

Questions

Why does my marker flicker or disappear?

The draw call is not running on every frame. Make sure the loop waits 0 ms while the marker should be visible.

Why is my marker floating or buried?

Adjust the Z value of the position. The examples subtract 1.0 from the point's Z; change that offset until the marker sits where you want it.

Can markers be drawn from a server script?

DrawMarker is a client native and has no server version in the natives reference. The server can send a client the locations, and the client draws them.

  • FiveM Blips: Sprite IDs, Color IDs and How to Add Them

    A FiveM blip is an icon on the map and minimap, created with AddBlipForCoord and styled with a sprite ID and a color ID. Common sprites, all color IDs from the official reference and Lua for adding, naming and removing blips.

  • Build a Small FiveM Phone App with NUI

    Build a Small FiveM Phone App with NUI

    Build a small phone-style NUI app first to learn the complete open, message, callback and close lifecycle. This example shows a session note that stays while the resource runs. It has no calls, messaging service, database or framework dependency; adding those requires separate server-side authorization and persistence.

  • How to Remove the Crosshair in FiveM (HideHudComponentThisFrame 14)

    How to Remove the Crosshair in FiveM (HideHudComponentThisFrame 14)

    Fast answer: FiveM servers remove the default GTA crosshair — HUD component 14 , the reticle — by running HideHudComponentThisFrame(14) every frame in a client script. The call must run on the client, inside a loop, because HUD components render again on the next frame. Below: the copy-paste resource, an optional player toggle command, and fixes for a crosshair that keeps coming back.