The /hud menu

Type /hud in game. This is where almost every setting lives.

Note

Tab names follow the language the player picked, so the labels you see may differ from the ones written here. See Translations.

Player settings

Saved per player, and restored on reconnect. Each player controls:

• Which widgets appear at all, and where on screen
• Colours — including the menu’s own accent
• Background opacity, down to fully transparent
• Language, if they want something other than the server default

Edit mode

Positioning is done by dragging, not by typing coordinates. Edit mode drops the HUD into a layer where every widget can be moved and resized directly, with snap guides between them.

Chat is hidden while edit mode is open, so it does not sit under what you are dragging.

Share codes

A layout can be exported as a share code and imported by another player, or on another server. Positions, colours and opacity travel; nothing else does.

Admin settings

These apply to everyone

Admin tabs are marked in red throughout the menu. The red is not an error state — it means this leaves your machine and changes the server for every player.

Visible only to players holding the command ace.

What is set there:

Setting	Effect
Seatbelt	Whether the HUD runs its own seatbelt, or leaves it to your script
Indicators	Same, for turn signals and hazards
Cruise control	Same, including the speed readout
Stress	Whether the HUD’s own stress engine runs, and which items relieve it
Crosshair	The NUI crosshair, since FiveM’s native one cannot be set by a resource
Server logo	Which logo shows, from config/logos/
Currency	The symbol used by the wallet widgets
Default language	What a player sees before choosing their own
Custom statuses	Your own status icons, static or 0–100
Widget locks	Requiring an item for a widget to be visible

Turning a feature off

Every feature the HUD provides can be turned off here. That is the supported way to run your own seatbelt, indicator or cruise script alongside it — turn the HUD’s version off, then feed the icons from your script with the exports.

While a HUD feature is on, it is the source of truth and external values are ignored.

Custom statuses

Statuses you define yourself, with your own icon and colour. Two kinds:

• Static — on or off, like a safe-zone marker
• Numbered — 0 to 100, like radiation or infection

A status can be fed by polling or pushed from your script. The push form is exports.hud:SetCustomStatus, documented in Exports.

Support

The last admin tab reports what the HUD detected and what has failed since start-up, and builds a report you can paste into a support channel. See Troubleshooting.