Analytics runs only if you accept. No names, codes or payment details are sent, and shopping works the same either way. Details: privacy and cookies.

  • Necessary Keeps your cart and this choice in your browser so the store works. We ask again after 12 months.
    Always on
  • Analytics (PostHog) Counts pages, clicks and store actions with your device type and rough location, and may record your visit with typed text hidden. Its cookie lasts 365 days. Data is stored in the EU. If you log in with Cfx.re, your visits count as one customer on each device where you accept, and your Cfx.re name is never sent.
    Off
  • Videos Product videos load from YouTube (Google) only when you press Play. YouTube may store data on your device. If you reject, Play opens the video on youtube.com in a new tab instead.
    When you press Play

With analytics on, the site keeps this visit's campaign source in this tab until you close it.

Change your choice any time with Cookie settings at the bottom of the page.

How police evidence works on a FiveM server

On a FiveM server, evidence is what a crime leaves behind for police to find. Shots drop casings, wounds leave blood, and a driver leaves fingerprints in the car. Officers find each piece, collect it and analyse it to put a name to a scene.

Our Realistic Evidence System V2 runs this on ESX, Qbox and QBCore. The numbers in this guide are the shipped defaults, and most of them sit in its config.lua for you to change.

What leaves evidence

  • Shooting. Each shot can drop a bullet casing near the shooter and a fragment on the ground where the bullet lands. A wall or other surface also gets a bullet hole. People and vehicles don’t.
  • Getting hurt. A player hurt by a weapon leaves a blood sample where they stand.
  • Driving. A non-police player who drives a car without gloves leaves a fingerprint in it. The car keeps only the latest driver’s print, for 120 minutes.
  • Gunshot residue. Shooting also puts GSR on the shooter’s hands.

A stun gun leaves no fragment, bullet hole or GSR. Each weapon list sits in config.lua, so you can add more.

Who the evidence points to

Some pieces carry the DNA of the player who left them. Blood and fingerprints always do. A casing does half the time. Fragments from a shooting and bullet holes name nobody.

Gloves stop DNA on casings and fingerprints, but blood still gives it away. The script reads gloves from the character’s arms clothing, in HasGloves in client/main_editable.lua.

With ox_inventory, qs-inventory or qb-inventory, every casing also carries the gun’s serial number. On ESX with its default inventory, casings show no serial.

One option makes it harder. With Config.UseFingerprintSystem = true, DNA shows a name only after police have scanned that person with the fingerprint_scanner item. The scan works within 3 metres and fails if the person wears gloves. It ships off.

How police find and collect it

  1. An officer holds a flashlight and aims it with the right mouse button. Evidence within 10 metres shows up on screen.
  2. They press E within 2 metres to collect it. With ox_inventory, qs-inventory or QBCore, each piece becomes an inventory item. On ESX with its default inventory, the script keeps it for the player instead.
  3. For a car, the officer sits inside and uses the uv_light item. “Fingerprints found” means they now carry the print.
  4. For GSR, they use a gsr_test_kit on a player within 3 metres. The result is “GSR Negative”, “GSR Positive (Recent)” within 10 minutes of shooting, or “GSR Positive (Aged)” after that. Each test uses up a kit.

GSR fades after 60 minutes. A gsr_cloth removes it, and so do 15 seconds in water. Evidence nobody collects disappears after 360 minutes, and the server clears it every 10 minutes.

Only jobs in Config.PoliceJobs count as police. It ships with police and sheriff, from grade 0.

Analysis, lockers and the scene

Police analyse evidence at the points in Config.AnalyzeCoords, where an “Analyze Evidence” prompt shows within 2 metres. Set them to your own station. The analysis screen shows each piece with its tag, time, DNA, weapon and serial number or plate, in a 3D viewer or as plain text.

On the same screen, officers create named lockers, store evidence in them and take it out. Lockers hold evidence only. Whatever goes in stays until an officer deletes it.

The evidence_camera item rebuilds a scene where the officer stands. It marks every piece they carry that was found within 20 metres, at the spot where it lay. Use it again to leave the view.

Criminals can clean up too

Anyone holding a flashlight sees ground evidence. They can collect it with E, or remove it for good with Y. A careful criminal can wipe a scene before police arrive. Analysis, lockers and the UV light stay police-only, and so does the GSR kit as shipped.

To keep ground evidence for police alone, return false for other jobs from CanSeeEvidence, CanSeeCollectOption and CanSeeRemoveOption in client/main_editable.lua.

What it connects to

  • Inventory: ox_inventory, qs-inventory or qb-inventory. The item list for each is in the script’s README.txt, and how to add items to ox_inventory shows where they go.
  • MDT: with Config.UseMDT = true, every piece put in a locker gets an entry on the police page of All-in-One MDT V2, and taking it out removes the entry. Start tk_mdt before tk_evidence. It ships off, and the MDT is sold separately.
  • Ambulance Job: with Config.UseTKEvidence = true in Advanced Ambulance Job, a medic who removes a bullet gets a bullet fragment carrying the patient’s DNA. It also ships off. The medic’s side is in how death works in FiveM.
  • Your own scripts: the client exports saveEvidence and saveFingerprint leave evidence on the ground. The server export addEvidenceItem hands it straight to a player.

For how evidence fits with the jail, dispatch and MDT, see how our police scripts work together.

What to check before you choose

  • Your inventory. Items and serial numbers need ox_inventory, qs-inventory or QBCore. Plain ESX gets neither.
  • Who may see evidence. Decide whether criminals should be able to clean up, and edit the three functions if not.
  • Your departments. Add every other police job to Config.PoliceJobs.
  • Known problems. The evidence docs answer the common setup questions.
  • See it in game. The showcase on YouTube runs 2:09.

Realistic Evidence System V2 is sold on its own, and it’s also in our Essential and Ultimate plans. Compare the plans if you run several of our police scripts.

The script in this guide

  • Casings, blood and fingerprints to collect, analyse in 3D and rebuild into a crime scene.

    Supports ESX, Qbox and QBCore

    Top 3 evidence script on FiveM

    550+ servers (5Metrics, checked 11 November 2026)

    €14.99+ VAT at checkout, one-off

Server counts: 5Metrics, checked 11 November 2026. Detected servers running each script, rounded down.

Spin for a discount code

Every spin gets a code; chance sets its size.

Cfx.re login and joining our newsletter are needed for your code.

Checking whether you can spin…

Odds for every spin
DiscountChanceMinimum order
15% off60%None
20% off28%None
25% off10%€30.00 + VAT
30% off2%€39.00 + VAT

Wheel codes work on scripts, bundles and a monthly plan's first payment, not on gift cards. One spin per Cfx.re account every 90 days. Each code is valid for 14 days and works once, with one code per order.