🎥Bodycam
Preserve incidents from an officer's body-worn perspective and manage the resulting evidence.
Bodycam gives public-safety personnel a body-worn evidence workflow inside FiveM. It preserves activity before and after an incident, supports manual and automatic recording triggers, and lets authorized staff review the event later from the recorded wearer's perspective.

Preserve the wearer's perspective
Each eligible wearer receives one server-authorized camera attached to the configured ped bone. The rolling pre-event buffer helps preserve what led up to an incident instead of starting only after the record button was pressed.
A recording can begin from:
A manual recording or saved buffer
The wearer's weapon discharge
Configured wearer damage or officer-down thresholds
A panic activation
A configured dispatch or integration trigger
If another trigger occurs during an active recording, Bodycam adds an evidence marker to the same timeline instead of creating a duplicate recording.
Review historic evidence
Bodycam reconstructs the recorded incident inside FiveM from the saved gameplay state. Reviewers can play, pause, seek, skip, step through the timeline, change replay speed, and return to the single recorded bodycam perspective after the original wearer and scene are gone.
The standard replay is not a conventional video file. Optional video generation, external storage, CAD, or Discord workflows require a separately configured Events Core integration.
Control access and custody
ACE permissions and optional framework job grades control who can wear and record with a bodycam, review their own or departmental evidence, add notes, classify records, lock or archive evidence, change retention, and delete unprotected records.
Wearer eligibility can use permission/job access by itself, accept any enabled permission, inventory, or EUP check, or require every enabled check. EUP and inventory eligibility are evaluated on the server through editable integration adapters.
How it works
An eligible, authorized player joins or changes into an approved duty state.
Bodycam binds one camera to the server-observed player ped.
A manual or automatic trigger starts a recording with pre-event context.
The finalized record appears in the Body-Worn Camera Evidence terminal.
An authorized reviewer searches for the record and reconstructs the incident from the recorded perspective.
Requirements
Events Core
Free required package: download Events Core
Events Bodycam
Paid Bodycam DLC from the Sonoran Store
FXServer
A current FiveM server with OneSync enabled
Permissions
ACE permissions or a supported framework job setup
Framework
Standalone by default; ESX, QBCore, and Qbox context can be configured
Database
No SQL database is required by the default configuration
Start here
Follow Installation to install Events Core and Bodycam in the correct order.
Review Configuration, Wearer Setup, and Permissions.
Test manual and automatic Recording with an eligible wearer.
Open the finalized record and test Playback and Evidence.
Building an integration? See the Developer API for supported exports and lifecycle events.
For help, see Troubleshooting or contact Sonoran Software support.
Last updated
Was this helpful?