Best FiveM Police MDT Scripts Compared (2026)

Your cops are alt-tabbing to a Google Doc to check if someone has warrants. Or worse, they’re just making it up. Either way, your police department needs an MDT and you’re trying to figure out which one won’t be a headache to install and maintain.

I’ve tested, installed, and troubleshot most of the major MDT scripts floating around the FiveM ecosystem. Here’s an honest breakdown of what’s out there, what each option does well, and where each one falls short.

What a Police MDT Actually Does

Before comparing anything, let’s be clear on what we’re talking about. A Mobile Data Terminal is the in-game tablet or laptop that police officers use to look up citizens, check vehicle registrations, manage warrants, file reports, and coordinate with dispatch. It’s the central nervous system of any serious police department RP.

A good MDT should do these things without making officers want to quit the server:

• Search citizens by name or state ID
• Run vehicle plates
• Create and manage warrants and BOLOs
• Write incident reports
• Track evidence
• Handle dispatch calls
• Manage department rosters and ranks

If you’re running a server where police RP matters — and on most RP servers, it’s the backbone of the whole experience — your MDT choice shapes how every officer interaction plays out.

ps-mdt (Project Sloth) — The Free Standard

Framework support: QBCore, Qbox (via ps_lib) Cost: Free and open source GitHub: Project-Sloth/ps-mdt

ps-mdt is the MDT most QBCore servers end up using, and for good reason. It’s free, actively maintained, and covers all the core features you’d expect. Officers press F11 or type /mdt and get a clean interface built with Svelte 5.

What it does well:

Citizen lookups, vehicle searches, warrant management, BOLO system, incident reports, evidence tracking, bodycam and security camera feeds, dispatch integration — it’s all there. The permission system is solid too, letting you control what each rank can access. A patrol officer doesn’t need to see the same screens as the chief of police.

The fact that it works on both QBCore and Qbox through ps_lib means you’re not locked in if you decide to migrate frameworks down the road.

Where it falls short:

It’s QBCore/Qbox only. If you’re running ESX, this isn’t an option without heavy modification. The UI, while functional, isn’t winning any design awards — it’s clean but basic. And because it’s a community project, you’re dependent on community support. The GitHub issues tab is your help desk.

Setup requires some SQL work and config editing. If you’re not comfortable with that, read through our script installation guide before jumping in.

Best for: QBCore or Qbox servers that want a full-featured MDT without spending anything. If your budget is zero and you’re on QB, this is the obvious choice.

pScripts Police MDT v2 — The Multi-Framework Premium Pick

Framework support: ESX, QBCore, Qbox Cost: Paid (check pScripts Tebex for current pricing) Escrow: Yes (Asset Escrow)

pScripts MDT v2 is a paid option that immediately solves the biggest limitation of ps-mdt: framework support. It runs on ESX, QBCore, and Qbox out of the box. That alone makes it relevant for a huge chunk of the community.

What it does well:

The feature list is deep. Citizen and vehicle search, recent lookups, notes system, fines and warrants, evidence management, incident reports, a faction garage, employee management, tariff lists, and detailed operational tools. The UI is polished — noticeably more refined than ps-mdt’s interface.

Framework auto-detection means you don’t have to manually configure which framework you’re running. It figures it out. That’s a small thing, but it’s the kind of detail that separates a premium script from a free one.

Where it falls short:

It’s escrowed, which means you can’t dig into the source code to customize behavior beyond what the config exposes. If you need something the config doesn’t offer, you’re submitting a feature request and hoping. This matters more than you’d think — every server has unique RP rules, and sometimes you need to tweak how warrants work or add a custom field to reports.

Price is also a factor. For a smaller server just getting started, spending money on an MDT when ps-mdt exists for free is a tough sell unless you specifically need ESX support or the polish matters to your community.

Best for: ESX servers that need a solid MDT, or any server where UI quality and multi-framework support justify the cost.

Deltarix MDT V2 — The Feature-Heavy Option

Framework support: ESX, QBCore, Qbox Cost: Paid (lifetime purchase or monthly subscription) Docs: docs.deltarix.store

Deltarix takes a kitchen-sink approach. Their MDT V2 packs in citizen search with photos and detailed histories, property tracking, vehicle and job lookups, license management, galleries, incident logging with auto-detected locations, and related-incident linking.

What it does well:

The incident system stands out. Auto-detecting incident locations and letting you link related incidents together is genuinely useful for long-running investigations. If your server does serious detective RP, this kind of feature makes a real difference. The citizen profiles are detailed too — stats, properties, vehicles, galleries, notes. It gives officers a complete picture.

The subscription option is interesting if you don’t want to drop a lump sum upfront. Not many FiveM script developers offer that.

Where it falls short:

Their own documentation mentions Qbox compatibility issues. That’s a red flag if you’re on Qbox or planning to migrate. Feature bloat is also a real concern — not every server needs incident linking and property tracking in their MDT. More features means more things that can break, more database tables, and more performance overhead to worry about.

Documentation could be more thorough. When you’re paying for a script, you expect solid docs that cover every config option and edge case.

Best for: Servers with active detective RP and investigation storylines that benefit from detailed incident management. Worth the money if you’ll actually use the advanced features.

Pixel Precision Police MDT — The All-in-One Tablet

Framework support: Framework-agnostic (works with any framework) Cost: Paid Docs: docs.pixelprecision.dev

Pixel Precision markets their MDT as an all-in-one solution that works with any framework. The tablet interface is designed to feel like a real police MDT you’d see in an actual patrol car — sleek, intuitive, and functional.

What it does well:

Framework-agnostic design is the headline feature. ESX, QBCore, Qbox, custom frameworks — it’s supposed to work with all of them. That’s appealing if you’re running something non-standard or if you’ve heavily modified your framework. The UI design leans into realism, which matters for immersion-focused servers.

Where it falls short:

Being framework-agnostic can mean it’s not as deeply integrated with any specific framework’s systems. A script that knows how QBCore handles jobs and licenses natively can do more than one that abstracts everything away. You might find yourself needing bridge scripts or additional configuration to get the tight integration that ps-mdt gives QBCore out of the box.

Best for: Servers running custom or heavily modified frameworks where other MDTs won’t plug in cleanly.

Free vs Paid — When It’s Worth Spending Money

I’ve written about this more broadly in our free vs paid scripts section, but for MDTs specifically:

Go free (ps-mdt) if:

• You’re on QBCore or Qbox
• Your police department doesn’t need anything exotic
• You’re comfortable doing some setup and config work
• Budget is tight and you’d rather spend on other scripts

Go paid if:

• You’re on ESX (ps-mdt doesn’t support it)
• UI quality matters a lot to your community
• You need specific advanced features like incident linking
• You want official support channels instead of relying on GitHub issues

Most servers can run perfectly fine on ps-mdt. I’ve seen servers with 100+ players use it without issues. The paid options earn their price when you have specific needs that the free option doesn’t cover.

Performance Considerations

Every MDT involves database queries — citizen lookups, vehicle checks, warrant searches. On a busy server, that adds up. A few things to watch for regardless of which MDT you pick:

Database indexing matters. If your MDT is slow when officers search for citizens, it’s probably a database issue, not the script itself. Make sure your players table and vehicles table have proper indexes on the columns the MDT searches. I covered database performance more broadly in the resmon guide, and the same principles apply here.

Client-side rendering costs. MDTs with fancy UIs — animated elements, live maps, real-time updates — consume client FPS while the tablet is open. This is usually fine, but test it on lower-end machines. Your players aren’t all running RTX 4090s.

-- Quick way to check MDT resource usage
-- Open the MDT in-game, then run in F8 console:
resmon 1
-- Watch the MDT resource's ms value. Under 0.5ms is fine.
-- Over 1ms while open means the UI is too heavy.

NUI overhead. All of these MDTs use NUI (HTML/JS rendered in-game). If you’re already running a heavy phone script, a custom HUD, and gameplay scripts like our LMX StoreMaster or LMX Trap & Stores, adding a complex MDT on top means multiple browser instances fighting for resources. Keep an eye on total NUI overhead.

Installation Tips That Apply to All MDTs

Regardless of which MDT you choose, here’s what I’d recommend:

Test on a local server first. Don’t install a new MDT on your live server. Set up a localhost test environment, install it there, and make sure everything works before your 50 active officers log in and find a broken tablet.

Back up your database. MDTs create tables. Some MDTs migrate data from other MDTs. If something goes wrong, you want a rollback path. A simple mysqldump before you start saves hours of pain.

Read the config file completely. Every MDT has config options that change behavior significantly — things like which jobs can access the MDT, what ranks can issue warrants, whether civilians can see their own records. Skipping the config and using defaults means you’re leaving features on the table.

Check your dependencies. ps-mdt needs ps_lib. pScripts needs its own bridge. Deltarix has its own dependency chain. Missing a dependency is the number one reason MDT installs fail. Check the documentation, install everything it asks for, and verify your fxmanifest.lua start order is correct.

Which MDT Should You Pick?

Here’s the honest answer: start with ps-mdt if you’re on QBCore or Qbox. It’s free, it works, and it covers what 90% of police departments need. If you hit a wall where you need ESX support, better UI, or advanced investigation tools, then you have a clear upgrade path to the paid options.

If you’re on ESX, pScripts is probably your best bet for a well-rounded MDT that doesn’t require you to switch frameworks.

If detective RP and long-running investigations are a big part of your server’s identity, Deltarix’s incident system is worth looking at.

And if your framework situation is unusual, Pixel Precision’s agnostic approach saves you from compatibility headaches.

Whatever you pick, pair it with a solid dispatch system and make sure your officers actually know how to use it. The best MDT in the world is worthless if your PD is still alt-tabbing to Discord to check warrants.

Need help with other aspects of your server setup? Check out our best scripts guide for the full list of essentials, browse our free scripts collection, or hop into our Discord if you’ve got questions.