Mods & customization Guide

FiveM blip creator: Lua generator, sprite IDs and colours

Generate a client-side FiveM map blip in Lua. Enter coordinates, a sprite and colour ID, then review the code with official Cfx references and staging checks.

FiveM blip creator: Lua generator, sprite IDs and colours — original Magnate explanatory diagram Original explanatory diagram · Not game footage
Creator tool

Build a client-side map blip

Enter your location and IDs from the Cfx blip reference . The starting coordinates are a demonstration, not a verified destination.

Review the demonstration or generate your own.

Runs in your browser. Formats one static client-side blip; it does not find coordinates, preview icons, validate ID availability, or add job restrictions. Coordinate and scale limits are this editor’s limits. Test the result in-game. No server connection is made.

Choose sprite and colour IDs from the right lists

The Cfx blip reference separates sprite IDs from colour IDs. A sprite selects the icon; a colour value styles it. Do not paste an icon number into the colour field because both happen to be numeric. The reference also describes friendly/enemy colour variants, so test the actual context rather than treating a colour name as a universal visual result.

This generator accepts numeric palette colours 0–85 and whole-number sprite inputs within its editor limit. It does not verify that a sprite exists in your installed build. Check the official visual reference, then inspect the result on your server. It does not generate hexadecimal colour input.

What the generated Lua does

The example creates one blip at the entered X, Y and Z coordinates. It then sets the sprite, colour, scale and short-range flag, and applies the supplied name through the blip-name text commands. These calls run in a client script. The code is a starting point, not a complete server resource.

The snippet includes a client resource-stop handler scoped to its own resource, with a RemoveBlip call. Restart behavior still belongs in your staging test: verify that starting, stopping and starting the resource gives the intended icon count. No game-runtime test is performed by this website.

Put the snippet in a client resource

Save the generated code as client.lua in a resource you control. Declare that file as a client script in the resource manifest. The minimal example below is for a dedicated test resource, not a replacement for an existing package’s complete manifest. Use the manifest builder when you need a starter with several script lists.

Minimal test resource manifest: fxmanifest.lua
fx_version 'cerulean'
game 'gta5'

client_script 'client.lua'

A map icon does not create the location or interaction

Placing an icon at a hospital, house or shop does not install its interior, register a job interaction or establish access permission. Keep the marker’s purpose separate from the gameplay resource. The generated client snippet has no role check and will run for clients loading that resource.

Use coordinates recorded for your intended location and environment. The demonstration values in the tool are editable examples, not a recommendation for where to place your resource. For a map package, test the entrance and relevant interaction separately from whether the map icon appears.

Verify one blip before adding many

Use a staging resource and a descriptive label. Compare the icon on the map and minimap, approach and leave the area, and check the short-range setting. Confirm the destination against the actual world location before sharing it with players.

Proposed blip acceptance checks
CheckExpected result to defineUseful evidence
PositionIcon matches the intended locationRecorded coordinates and world observation
SpriteThe chosen icon exists in the installed buildSprite ID and map view
ColourVisible colour is suitable in the actual contextColour ID and screenshot
RangeVisibility matches the short-range choiceNear and far observations
NameLabel is readable and identifies the destinationMap label and language
LifecycleStopping and restarting gives the intended icon countResource events and observed result

Tool limits and troubleshooting

The browser tool validates the input format and escapes the label for a Lua string. It rejects control characters and tilde formatting in labels, allows up to 80 UTF-8 bytes, and limits scale and coordinates for this editor. Those limits are not a statement of all values the game can accept. Changing an input clears the old output so the copy button cannot silently use stale code.

If the icon is absent, inspect the resource startup and client errors before changing every style value. If it is in the wrong place, compare coordinates first. If the style is wrong, check the sprite and colour separately. This is a static coordinate example, not an entity-following blip or a player-tracking system.

For the underlying environment, use our map-discovery and MLO guides. For packaging, use the fxmanifest guide. The generated example concerns current GTA V/FiveM and does not establish GTA VI compatibility.

Questions, answered.

Are FiveM sprite IDs and colour IDs the same?

No. They are separate inputs with separate reference lists. Check both before testing the icon.

Does this blip creator connect to my server?

No. Code generation happens in the browser. You must install, review and test the snippet in a resource you control.

Can I use the generator for a job-only blip?

The generated code has no job restriction. Use an appropriate framework integration and test the intended access and visibility rules separately.

Sources & editorial notes

Source review: November 7, 2026. Platform announcements can change. This guide separates published facts from Magnate’s original analysis and preparation advice.

  1. Cfx — Blip sprites and colours Official sprite and palette reference; verify availability in your build.
  2. Cfx native source — AddBlipForCoord Coordinate blip creation signature; adjacent HUD definitions document styling calls.
  3. Cfx native source — Blip name text commands Text-command pairing for a blip label.
  4. Cfx native source — RemoveBlip Removal and creating-script ownership note.
  5. Cfx — onClientResourceStop Client resource-stop event and resource-name parameter.
  6. Cfx — Resource manifest Official manifest metadata and file declarations.

Published by an independent editorial brand. Read our editorial standards.

Find your next move

Search the Magnate guide library.

Browse every guide