> For the complete documentation index, see [llms.txt](https://docs.sonoransoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sonoransoftware.com/store/bodycam/playback.md).

# Playback and Evidence

Search Bodycam evidence, replay the recorded perspective, and manage notes, classifications, locks, archives, and retention.

Finalized recordings appear in the Body-Worn Camera Evidence terminal for authorized reviewers. Press F6 or run /bodycamreview, then search or filter the evidence list and select a record.

## Find a recording

The terminal can search the information attached to accessible evidence, including:

* Recording ID
* Officer name or callsign
* Wearer model
* Department
* Incident or case number
* Citation number
* Arrest-report number

You can also filter by classification and finalized state. The result list is permission-filtered, so users see only their own, departmental, or all Bodycam evidence according to their access.

## Recorded bodycam perspective

Every Bodycam recording retains one body-worn camera definition. The shipped view is attached to the upper-spine bone with a 78-degree field of view. The recording keeps its captured perspective, so a reviewer can return after the original wearer or scene is gone.

When exact animated bone coordinates were unavailable to the server during capture, the recorded transform may be marked approximate. Verify camera placement with the peds and uniforms used by your server.

## Playback controls

Open **Structured Replay** from the selected record. The terminal supports:

* Play and pause
* Restart
* Seek with the timeline
* Skip backward or forward 10 seconds
* Step backward or forward
* Playback speeds of 0.25x, 0.5x, 1x, 2x, and 4x
* Exiting replay and returning to the evidence terminal

Bodycam recreates the incident inside FiveM from recorded gameplay state. A normal Bodycam replay is not an MP4 or continuous screen recording. Separate video generation or upload requires an optional compatible processing setup.

<figure><img src="https://954277862-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FA1LA3ay59CDyDKnfXPfc%2Fuploads%2Fgit-blob-c60bb077c70cfba42e6343d6f53852627b691b70%2Fbodycam-recorded-perspective-replay.webp?alt=media" alt="Bodycam structured replay with timeline and playback controls"><figcaption><p>Review the reconstructed timeline from the recorded bodycam perspective with markers and interactive playback controls.</p></figcaption></figure>

## Evidence details

Depending on permissions, reviewers can:

* Set the classification
* Add or update incident, case, citation, and arrest-report numbers
* Add operational notes
* Lock or unlock the record
* Archive or unarchive the record
* Change retention days
* Delete an unlocked, unpreserved record with a substantive reason

Locked records cannot be edited or deleted until an authorized reviewer unlocks them. Preserved records cannot be deleted. Deletion is permanent and requires bodycam.delete.

<figure><img src="https://954277862-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FA1LA3ay59CDyDKnfXPfc%2Fuploads%2Fgit-blob-452f8a466db83ca01d7ad3da7d8f259bb15b290e%2Fbodycam-evidence-custody.webp?alt=media" alt="Bodycam evidence custody controls for locking, archiving, retention, and deletion"><figcaption><p>Authorized evidence custodians can protect, archive, retain, or delete records from the review terminal.</p></figcaption></figure>

## Shipped classifications and retention

| Classification              |           Retention |
| --------------------------- | ------------------: |
| routine                     |             30 days |
| traffic\_stop               |             90 days |
| arrest                      |            180 days |
| use\_of\_force              |            365 days |
| officer\_involved\_shooting | No automatic expiry |
| complaint                   |            365 days |
| training                    |             30 days |
| indefinite                  | No automatic expiry |

Changing a record's classification applies that classification's configured retention policy. A retention value of 0 means the record has no automatic expiry. Bodycam accepts configured and manual values from 0 through the camera policy maximum of 3,650 days.

Review your local evidence policy and available storage before changing retention. Record data is stored under eventsCore/data/recordings by default; back it up securely before updates or storage changes.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sonoransoftware.com/store/bodycam/playback.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.