Default FiveM vehicle trunks are inventory slots, nothing more. This script treats the trunk as a physical space officers actually interact with — opening it reveals a laid-out interface of props, weapons, and clothing that can be pulled out, placed, or equipped directly. It’s the difference between a police loadout that feels procedural and one that looks like an officer getting geared up at their patrol car.

The per-vehicle layout configuration is where this becomes genuinely useful for server owners. You can define exactly which props and items appear in each vehicle model’s trunk, so a marked unit carries different gear than an unmarked detective car. That specificity feeds into department hierarchy and role differentiation without requiring separate inventory setups for every rank.

Key Features

• Interactive trunk interface with visual prop layout — not a flat inventory menu
• Keyboard and mouse navigation for selecting and equipping trunk contents
• Automatic prop detection on vehicle spawn — no manual configuration per session
• Per-vehicle layout configuration for granular department loadout control
• Configurable actions: item grants, prop deployment, and clothing changes per slot
• Job-based access restrictions — restrict trunk access to officers or specific ranks
• ox_target and qb-target both supported for interaction prompt
• Debug mode for configuring trunk layouts on new vehicle models
• Full client synchronisation — trunk state visible to nearby players
• 0.00ms idle / 0.03ms during active use

Framework Compatibility

Supports ESX, QBCore, and Qbox. Works equally well for police, fire, EMS, and civilian vehicles — any department that needs organised trunk access benefits from the same setup.

The 0.03ms active reading is realistic: it’s only drawing when someone has the trunk open, so it won’t compound across multiple officers simultaneously. EMS and fire department operators can apply the same resource to their vehicles with different item sets configured. Rated 4.56/5 across nine reviews.