FiveM color codes: text tags, RGB, blips and vehicle paint

Choose the color namespace first

Before copying a number or code, identify where it will be consumed. A native text label, map blip, vehicle paint menu and browser-based UI do not share a universal palette. The same number can mean different things in different APIs.

Common native text color codes

Cfx’s text-formatting reference documents the following tags for game text labels. Whether a particular resource parses them depends on its renderer. These examples are not a promise that every server chat or notification component accepts them.

Reset the text color after the intended phrase

Cfx documents ~s~ as a reset to the current context’s default, not a fixed color guarantee. Use it after the phrase you intend to highlight so the following text is not accidentally part of the same colored span.

For example, ~g~Ready~s~ for delivery is an original sample formatted string for a renderer that supports Rockstar tags. If the tildes appear literally, inspect the resource’s expected input format instead of substituting unrelated numeric IDs.

~g~Ready~s~ for delivery

Hex and RGB conversion does not find a game ID

The converter above translates a six-digit web hex color into three decimal channels from 0 to 255. For example, #FA3F4C becomes 250, 63, 76. This mathematical conversion is useful only when the target setting explicitly accepts RGB.

It does not select the nearest vehicle paint, HUD or blip index. A paint finish, game lighting or UI palette can produce a different visible result from a browser swatch. Use the exact game reference for indexed colors and test the intended renderer.

Vehicle paint and map blips need their own references

The official Cfx vehicle-color reference organizes indexed paint colors by finish. For example, metallic index 0 is Black and metallic index 27 is Red. Those are vehicle references, not text tags or RGB triples. Confirm what your vehicle menu or native expects before passing a value.

For map icons, the blip guide explains its own IDs and builder. Keep icon sprite selection and color selection separate. A correctly colored icon in one API does not establish the matching text color or vehicle paint.

Diagnose a color that does not apply

Start with the exact resource, field name and documented value type. If a tag is shown literally, check whether the renderer supports formatting. If an RGB value is ignored, check whether the setting actually expects an index or CSS value. If the wrong shade appears, compare the intended palette and context.

Keep a copy of the original value and change one field at a time. Compare the same UI state or vehicle scene after the change, then reconnect if the resource saves settings. This guide’s format reference is source-reviewed; Magnate has not executed the example in a game client.

Keep color choices readable

Use a label, icon or text meaning alongside color so status does not depend on shade alone. Check small text and muted colors against the actual background, especially in bright and dark gameplay scenes. A visually attractive browser swatch is not a readability test for the game UI.

These references concern GTA V/FiveM. They do not establish GTA VI color APIs or future mod support. Use the chat and NUI guides for those specific rendering systems rather than treating this as a universal styling command.

Questions, answered.