67,700 Videos and Counting: The Body Camera Evidence Crisis

In 2025, the District Attorney's office in Jefferson County, Colorado, processed 67,700 body-worn camera videos totaling more than 41,000 hours of footage. Three years earlier, in 2022, those numbers were 36,000 videos and 24,000 hours. The volume had nearly doubled in thirty-six months.

DA Alexis King's office reported these figures to Colorado Public Radio in January 2026, and the numbers illustrate a crisis that no one in criminal law can afford to ignore. Each felony attorney in Jefferson County carries approximately 100 active cases. Each case involves an estimated four to six hours of body camera footage. That means a single attorney must review roughly 400 hours of video — and under Colorado law, the prosecution must provide discovery within 21 days.

Consider what this looks like in practice. King described what she called a "run-of-the-mill vehicular homicide case" — not a mass shooting, not a terrorism investigation, but a routine felony. That single case generated 362 photographs and up to 90 hours of body camera footage. An attorney working eight hours a day, watching nothing but video, would need more than eleven consecutive workdays to review the footage from one case. That same attorney has ninety-nine other cases on their desk.

Jefferson County is not an outlier. It is a preview. The same pressures that produced 67,700 videos in a mid-sized Colorado county are present in every jurisdiction that has deployed body cameras — which, as of 2025, is nearly all of them.

The Scale of Body Camera Deployment

Body-worn cameras have gone from experimental to ubiquitous in less than a decade. Approximately 73% of general-purpose law enforcement agencies in the United States now use body cameras, according to recent federal survey data. The Bureau of Justice Assistance reported in 2016 that video evidence was involved in approximately 80% of crimes — a figure that has only grown as cameras have become standard equipment. Among the 75 largest police departments in the country, only Portland, Oregon, had not deployed body-worn cameras as of 2025.

The market reflects this adoption. Axon Enterprise (formerly TASER International) controls approximately 70% of the body camera market through its Evidence.com platform. When a law enforcement agency deploys body cameras, Axon is overwhelmingly likely to be the vendor, and Evidence.com is overwhelmingly likely to be where the footage lives — at least while it remains in agency custody.

The Department of Justice and state legislatures have invested heavily in body camera programs. Federal grants through the Bureau of Justice Assistance have funded thousands of deployments. The policy rationale is sound: body cameras create an objective record of police-citizen encounters, supporting both accountability and officer protection. But the policy conversation has focused almost entirely on recording the footage. It has given comparatively little attention to what happens when that footage becomes evidence in a criminal proceeding and must be shared with the defense.

The Floating Copies Problem

When a prosecutor discloses body camera footage to the defense, the footage leaves the controlled environment of Axon Evidence or whatever platform the agency uses. The method of transfer varies by jurisdiction and often by individual case. Defense attorneys may receive footage via DVD, USB drive, cloud download link, or an Axon Evidence sharing portal with time-limited access.

In Florida's 20th Judicial Circuit, for example, Evidence.com sharing links expire after 120 days. If the defense needs to revisit footage seven months into a case — a routine occurrence in felony litigation — the original link is dead. The defense must request re-sharing, and the access log from the original sharing period is no longer available to them.

But the expiring link is not the core problem. The core problem is what happens the moment the defense downloads the footage. At that instant, the file becomes what we call a "floating copy" — a piece of evidence that has been disconnected from the original audit trail. No system is tracking who accesses it. No hash verification travels with it. No chain of custody documentation accompanies it.

The defense attorney downloads the footage to a hard drive. A paralegal copies it to a shared folder. An expert witness receives it on a USB drive. Co-counsel gets it via email attachment. Each copy floats free of any documented chain. If the footage is leaked to the media — as has happened in numerous high-profile cases — there is no way to determine which copy was the source. If opposing counsel challenges the integrity of the defense's copy, there is no contemporaneous documentation to prove it has not been altered.

The agency that recorded the footage has a chain of custody. Axon Evidence has access logs. But the moment the footage crosses the discovery threshold and enters the defense's hands, the documented chain ends. Every subsequent interaction is invisible.

Authenticating Body Camera Evidence at Trial

When body camera footage is offered into evidence, the proponent must authenticate it under FRE 901(a) by producing sufficient evidence to support a finding that the item is what the proponent claims it is. For video evidence, courts have recognized two distinct theories of authentication.

Illustrative evidence theory. A witness with personal knowledge testifies that the video "fairly and accurately represents" what occurred. The witness does not need to have seen the recording being made; they need only testify that the video depicts what they observed. This is the traditional approach, and it works well for short clips where a percipient witness can confirm the contents.

Silent witness theory. When no witness can testify to the events depicted — because the camera was operating autonomously, or because the relevant portion occurs when no witness was present — the proponent must instead lay an adequate foundation for the accuracy of the process that produced the recording. This requires evidence of how the camera system works, how the footage was stored, and how it was preserved from recording to trial. The silent witness theory places a premium on chain of custody documentation because the recording itself is the witness.

The Virginia Supreme Court addressed body camera authentication directly in Baez v. Commonwealth (December 2024) — the first time Virginia's highest court ruled on the admissibility of body-worn camera footage. The court held that BWC video is not inherently testimonial and may be admitted under either the illustrative evidence or silent witness theory, depending on the circumstances. The decision confirmed that body camera footage is subject to the same authentication requirements as any other video evidence, with no special presumption of reliability based on its law enforcement origin.

Under either theory, chain of custody documentation strengthens the foundation. Under FRE 902(13), electronic evidence can self-authenticate through a written certification describing the system used to generate, store, and verify the evidence. A defense attorney who can produce a SHA-256 hash computed at the time of download, a complete access log documenting every viewer, and a certification attesting to the integrity of the process has an evidence package that is resistant to challenge. A defense attorney whose foundation is "I downloaded it from Axon eight months ago" does not.

Brady Obligations and Body Camera Footage

Brady v. Maryland, 373 U.S. 83 (1963), established that the prosecution's suppression of evidence favorable to the defense violates due process, regardless of the prosecution's good faith. The rule extends to impeachment evidence under Giglio v. United States, 405 U.S. 150 (1972), and the prosecution's obligation encompasses evidence known to the police, not just to prosecutors personally. See Kyles v. Whitley, 514 U.S. 419 (1995).

Body camera footage raises Brady issues in two distinct ways.

The footage itself may be exculpatory. BWC video that tends to negate the defendant's guilt, contradict a prosecution witness's account, or support an affirmative defense is Brady material. When officers wear body cameras, the objective record may capture details that no witness noticed or remembered — the defendant's compliance with commands, an officer's use of force, the actual sequence of events. If that footage is favorable to the defense, the prosecution has a constitutional obligation to disclose it.

The metadata may itself be exculpatory. Body camera systems generate extensive metadata: activation timestamps, GPS coordinates, buffered pre-event recordings, and deactivation logs. This metadata can establish when a camera was turned on or off, where the officer was standing, and whether there are gaps in the recording. A camera that was deactivated during a critical moment, or a GPS log that contradicts an officer's testimony about their location, is potentially exculpatory information that must be disclosed under Brady. Metadata that reveals selective activation and deactivation patterns may be relevant to impeachment under Giglio.

The volume problem compounds the Brady obligation. When a case generates 90 hours of footage, the prosecution must review all of it to identify material that may be favorable to the defense. Under Kyles, the prosecution cannot disclaim knowledge of evidence in law enforcement's possession. A failure to review body camera footage does not excuse a failure to disclose Brady material contained within it.

Failure to preserve relevant body camera footage may itself constitute a Brady violation. If body camera footage that should have been retained is overwritten, deleted pursuant to a retention policy, or lost due to system failure, and that footage was or may have been favorable to the defense, the due process implications are significant. The Supreme Court's framework in Arizona v. Youngblood, 488 U.S. 51 (1988), requires bad faith for destruction of potentially useful evidence to violate due process, but several state courts have applied more protective standards under their own constitutions.

The Casey Anthony Lesson: Why Cross-Checking Matters

The prosecution of Casey Anthony in 2011 remains one of the most instructive examples of what happens when digital forensic results are accepted without independent verification. The case demonstrates a principle that applies directly to body camera evidence: the tool that produces the evidence is not inherently trustworthy, and the process that handles it must be documented and verifiable.

Prosecutors relied on a forensic tool called CacheBack to analyze internet browser history from the Anthony family computer. CacheBack reported 84 visits to a website about chloroform — a finding that became central to the prosecution's theory of premeditated murder. But the tool was wrong. The actual browser history, when properly analyzed, showed a single visit. CacheBack had a software defect that counted each component of a web page (images, scripts, style sheets) as a separate "visit."

The error was compounded by a second forensic failure: law enforcement's forensic analysis examined only Internet Explorer's browser history. The Anthony family computer also had Firefox installed, and the Firefox history was never examined. The defense was able to exploit both failures — the flawed tool and the incomplete analysis — to undermine the prosecution's entire digital evidence case.

The lesson for body camera evidence is direct. When defense attorneys receive BWC footage through an opaque process — a download link, a DVD, a USB drive — they are trusting that the file they received is complete, unaltered, and identical to what was originally recorded. That trust is not a foundation. A foundation requires verification: hash comparison against the original, documentation of the transfer process, and an independent record of every subsequent access. The Casey Anthony case showed what happens when a forensic result is accepted on faith. The same vulnerability exists every time body camera evidence changes hands without documentation.

Defense Access: Emerging Case Law

As body camera footage has become central to criminal litigation, courts have begun to address the procedural framework for defense access. Two 2025 decisions illustrate the competing approaches.

State v. Chemuti (N.C. Supreme Court, 2025)

The North Carolina Supreme Court held that defense access to body camera recordings is governed by a specific statutory petition process. Under North Carolina's body camera statute, recordings are not public records and may only be disclosed through a court order upon petition. The court rejected the argument that general discovery rights provide an independent basis for access, holding instead that the legislature's specific statutory scheme controls. For defense attorneys in North Carolina, this means that obtaining body camera footage requires a formal petition to the court — an additional procedural hurdle that does not exist in most other jurisdictions.

Fuster v. Chatham (N.J. Supreme Court, 2025)

The New Jersey Supreme Court took a different approach, holding that subjects of body camera recordings have a right to disclosure of the footage. The decision recognized that individuals who are recorded by police body cameras have a cognizable interest in accessing the recording, and that this interest outweighs the government's interest in restricting access absent specific countervailing concerns such as an ongoing investigation or witness safety.

The contrast between Chemuti and Fuster illustrates the fragmented legal landscape for body camera discovery. There is no uniform national standard for how defense attorneys receive body camera footage, how long they retain access, what format it arrives in, or what documentation accompanies it. Each jurisdiction has its own rules, and within jurisdictions, individual agencies may impose their own practices. The result is that the same piece of evidence — an officer's body camera recording of an arrest — may arrive in the defense's hands via entirely different mechanisms depending on where the arrest occurred.

What is consistent across jurisdictions is the gap that opens after transfer. Whether the defense receives footage through a statutory petition in North Carolina, a disclosure right in New Jersey, or routine discovery in federal court, the chain of custody documentation ends at the point of transfer. From that moment forward, the defense is on its own.

What Needs to Change

The body camera evidence crisis is not a technology problem. Agencies have the technology to record, store, and manage footage at scale — Axon Evidence processes millions of recordings. Prosecutors have tools to review and organize massive volumes of video. The problem is structural: the chain of custody documentation that exists within the agency's system does not travel with the evidence when it is shared.

Four changes would close this gap.

Chain of custody documentation must travel with evidence. When body camera footage is disclosed to the defense, the original hash, the recording metadata, and the agency's access log should accompany the files. The defense should know, at the point of receipt, that the files are identical to what was originally recorded — not because they trust the agency, but because the hash proves it mathematically.

Every viewer must be identified. Once footage enters the defense's custody, every person who views it should be logged with their identity, the time of access, and their device. This is not surveillance; it is the same standard that agencies apply to their own personnel through Axon Evidence. If a paralegal, expert witness, or co-counsel reviews the footage, that access should be documented. If footage is leaked, the access log identifies who had access.

Every access must be logged. The access log should be continuous and tamper-evident from the point of receipt through trial. It should record not just who viewed the footage, but what they viewed, when, and from where. This log becomes the foundation for authentication under both the illustrative evidence and silent witness theories. It transforms "I downloaded it and it's been on my hard drive" into a documented, verifiable chain.

Integrity verification must be automatic. SHA-256 hashing at the point of upload, with verification at every subsequent access, ensures that any alteration is immediately detected. This eliminates the most common authentication challenge — the allegation that footage was modified after transfer — because the hash comparison provides a mathematically certain answer.

These are not aspirational standards. They are the baseline that any evidence management system should provide. Physical evidence has been handled this way for decades: documented transfer, identified custodians, logged access, and integrity verification at every stage. The fact that body camera footage routinely changes hands without any of these safeguards is an anomaly, not a norm.

The Volume Problem Demands Automation

Return to Jefferson County's numbers. An attorney with 100 active cases, each involving four to six hours of body camera footage, must manage roughly 400 hours of video. For each file, the attorney must compute a hash at receipt, log every access by every team member, maintain integrity verification through trial, and generate authentication documentation for any footage offered into evidence.

Doing this manually is not realistic. A paralegal computing SHA-256 hashes via command line for every file, maintaining spreadsheet access logs, and preparing hand-drafted certifications cannot keep pace with the volume that modern body camera programs generate. The process either collapses under its own weight or, more commonly, never starts — and the defense handles body camera footage the same way it always has, with no chain of custody at all.

This is where purpose-built evidence management tools become essential. Automated hash computation on upload, automatic access logging for every viewer, viewer identity watermarking that attributes each view to a specific individual, and one-click FRE 902(13) certification generation transform a process that would consume hours of paralegal time per case into something that happens in the background. The attorney and their team focus on reviewing the footage. The system handles the chain of custody.

The investment pays for itself quickly. A single authentication challenge that requires a foundation witness costs $3,000 to $5,000. A motion to exclude evidence based on chain of custody deficiencies costs $2,000 to $10,000 in attorney time to defend. A documented, automated chain of custody prevents both — not by winning the challenge, but by ensuring it is never made.

Conclusion

Jefferson County's 67,700 videos are not the ceiling. They are the floor. As body camera technology improves, as storage costs decline, and as agencies expand deployment to auxiliary units and specialized divisions, the volume will continue to grow. The 41,000 hours that DA King's office processed in 2025 will be the norm for mid-sized jurisdictions within a few years.

The legal framework is clear. Brady requires disclosure of favorable evidence. Authentication under FRE 901 and 902(13) requires a demonstrable chain of custody. The silent witness theory demands proof that the process which produced the recording is reliable. None of these requirements can be met by an attorney whose evidence management process consists of downloading files and storing them on a hard drive.

The gap between what the law requires and how body camera evidence is actually handled in practice is the body camera evidence crisis. Closing that gap requires chain of custody documentation that travels with evidence through every transfer, identifies every viewer, logs every access, and verifies integrity at every stage.

Attested provides the access audit trail documentation that traditional evidence sharing methods lack — SHA-256 integrity verification, viewer identity attribution through viewer identity watermarking, and complete access logs for every piece of evidence shared.