How do I remove the crosshair in FiveM as a player?

Open ESC → Settings → Display and set Reticule to Off. If your server uses vMenu, open vMenu and toggle Crosshair Off. If a custom HUD draws a crosshair, ask the server staff to disable it.

How can server owners globally disable the crosshair in FiveM?

Create a small client-side resource that hides HUD component 14 (reticle) every frame using HideHudComponentThisFrame(14), ensure the resource in server.cfg, and restart the server.

Can I remove the crosshair but keep sniper/marksman scopes?

Yes. In your client script, check the selected weapon and only hide the reticle for non-scoped weapons. Allow scoped rifles (e.g., SNIPERRIFLE, HEAVYSNIPER, MARKSMANRIFLE) to keep their scope overlay.

How do I disable the vMenu crosshair?

Open vMenu, go to Weapon or Misc settings, and toggle Crosshair Off. If the toggle is locked by permissions, ask an admin or enforce crosshair removal via a client script in your server.

A HUD or UI is still drawing a crosshair. What should I do?

Check the HUD/UI resource configuration for a crosshair setting and turn it off. If it’s HTML/CSS based, remove the element or set .crosshair { display: none !important; }. For JS/canvas-based UIs, comment out the render call.

Is the crosshair removal script compatible with ESX or QBCore?

Yes. The HideHudComponentThisFrame approach is framework-agnostic and works with ESX, QBCore, and standalone servers.

Does removing the crosshair affect aim-assist or first-person aiming?

No. Hiding the on-screen reticle only affects the visual overlay. It does not change player input, weapon spread, or aiming mechanics.

Can admins temporarily enable or disable the crosshair for events?

Yes. Add an admin-only command (e.g., /togglecrosshair) that switches a boolean in your client script and conditionally hides the reticle. Restrict the command via ACE permissions.

How can I enforce crosshair removal only in specific zones or arenas?

Wrap the hide-reticle call with your zone/dimension logic. For example, check if the player is inside your arena or matches a certain job/team before calling HideHudComponentThisFrame(14).

Will hiding the crosshair impact performance?

The call is very lightweight and safe to run each frame. If needed, profile with Resmon to verify usage; it typically shows negligible overhead on modern clients.

Remove the FiveM Crosshair: 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.

Last updated: June 25, 2026

Copyable client script

Create a small client resource and put this in client.lua:

CreateThread(function()
 while true do
 Wait(0)
 HideHudComponentThisFrame(14)
 end
end)

The official Cfx.re native reference lists HideHudComponentThisFrame as the native for hiding HUD components. Component 14 is the reticle/crosshair.

Minimal fxmanifest.lua

Place this next to client.lua in a resource folder, for example resources/[local]/no-crosshair/:

fx_version 'cerulean'
game 'gta5'

client_script 'client.lua'

Then add the resource to server.cfg:

ensure no-crosshair

Why it has to run every frame

HUD hiding is frame based. Calling the native once can look like it worked for a moment, but the reticle returns because GTA renders HUD components again on later frames. Keep the loop lightweight and do not add expensive logic inside it.

Player-side vs server-side crosshair removal

Goal	Best method
Remove the default GTA reticle for everyone	Use a small client resource with `HideHudComponentThisFrame(14)`.
Let players choose	Add a client setting or command that toggles the loop.
Remove a custom weapon HUD	Check the weapon/HUD resource. It may draw its own crosshair.
Stop monitors or overlays adding a dot	Check client overlays, monitor features, and graphics mods.

Optional toggle command

If your server wants a player toggle, use a local variable:

local crosshairHidden = true

RegisterCommand('crosshair', function()
 crosshairHidden = not crosshairHidden
 print(crosshairHidden and 'Crosshair hidden' or 'Crosshair visible')
end, false)

CreateThread(function()
 while true do
 Wait(0)
 if crosshairHidden then
 HideHudComponentThisFrame(14)
 end
 end
end)

Troubleshooting

If the crosshair still appears, another HUD or weapon resource may be drawing its own element.
If the resource does not start, verify the fxmanifest.lua setup.
If only one player sees a dot, check monitor overlays or graphics tools on that PC.
If you need a full HUD pass, compare FiveM HUD resources.

FAQ

Can this be done in server.lua?

No. HUD rendering is client-side. Trigger a client event if you need server logic, but call the native in client code.

Does this affect custom scopes?

It hides the default reticle component. Custom weapon scripts, scopes, or NUI overlays may still draw their own UI.

Server-side rollout checklist

Before adding this to a live roleplay server, test it with the weapons and HUD resources your players already use. A default reticle can be hidden by component 14, but many servers also run weapon overlays, custom scopes, or NUI HUDs. Those scripts may draw their own crosshair and need separate settings.

Create the resource on a staging server.
Test pistols, rifles, shotguns, melee weapons, and unarmed movement.
Check first-person and third-person view.
Open the inventory, radial menu, weapon wheel replacement, and HUD.
Ask one tester with a clean client and one tester with normal overlays to compare.

How to debug a crosshair that comes back

If the dot returns only while aiming, your code may not be running every frame. If it returns only with one weapon or one job, a weapon or police resource may draw the UI. If it appears only for one player, check monitor crosshair features, ReShade overlays, GPU overlays, or accessibility tools on that PC.

Good server policy wording

If your server bans external crosshairs, write the rule clearly: no monitor crosshair, no overlay crosshair, no third-party aiming dot. Then enforce it with staff review rather than relying only on a script that hides the default HUD reticle.

When the crosshair comes back

If the dot returns only while aiming, the client loop may not be running every frame. If it returns only with one weapon or job, another weapon, HUD or police resource may draw its own aiming UI. If it appears for one player only, check monitor crosshair features, GPU overlays, ReShade overlays and accessibility tools on that PC.

Server rule wording

If your community bans external crosshairs, say exactly what is banned: monitor crosshair, overlay crosshair, third-party aiming dot and modified HUD reticle. A script can hide the default GTA HUD component, but it cannot police every external display feature by itself.