How 40 Terabytes of Evidence Reshaped the D4vd Murder Case

The preliminary hearing in the D4vd murder case began on July 21, 2026, with no same-day result available at research time. That matters because this is not a post-hearing account of whether a judge found enough evidence to send the case toward trial. It is a pre-hearing look at how the case arrived here: after repeated continuances, a capital charge, and a discovery universe prosecutors have described as exceeding 40 terabytes—an amount roughly comparable, for review purposes, to about 40 million documents.[1][2]

For readers tracking the D4vd murder case preliminary-hearing evidence, the procedural story is not merely that the file is large. Large files are now ordinary. What makes this one useful to study is that the size has already altered the calendar before the court reaches the ordinary preliminary-hearing question: whether the prosecution can establish probable cause.

The calendar became a discovery record

The case did not simply drift from one hearing date to another. Public reporting shows a sequence in which the defense repeatedly sought more time while prosecutors continued producing a large digital record. The preliminary hearing was moved from May 1 to May 26, then to June 29, and finally to July 21, 2026.[3][4]

The most important number in that sequence may be smaller than 40 terabytes. By April 23, only about 30% of the evidence had been turned over to the defense, according to ABC7’s account of the hearing posture.[3] That percentage is the point at which volume becomes more than a storage problem. It becomes an argument about what counsel can responsibly do in court.

A preliminary hearing is not a full trial, but it is not a clerical checkpoint either. Defense counsel may need to test witness accounts, identify gaps in the prosecution’s theory, prepare cross-examination, and decide which issues to preserve. If most production remains outstanding, the defense can make a straightforward claim: it is being asked to litigate probable cause without enough of the record to know what it is confronting.

That does not require assuming bad faith by prosecutors, nor does it require treating every defense delay request as pure necessity. Delay helps the defense in many criminal cases. Witness memories do not improve, pressure on the prosecution increases, and the public urgency around a case can cool. But in this record, the visible basis for delay is not a vague appeal to complexity. It is a disclosed production problem measured in tens of terabytes and in a late-April turnover percentage that left most material still outside the defense’s hands.[2][3]

Forty terabytes is not one pile of documents

Court-centered descriptions of “digital evidence” can flatten the work. A terabyte count sounds like one large archive that needs to be copied, loaded, and reviewed. The public record in the D4vd case suggests something more difficult: a mixed evidence environment spanning device images, cloud data, communications, transactional records, delivery logs, surveillance video, and wiretap-derived material.

Prosecutors’ filings and related reporting have described discoverable material from phones, computers, and tablets; one account separately identified about 3 terabytes from iCloud alone.[2][5] The distinction matters. A phone extraction, a cloud export, and a surveillance video set do not create the same review problem. They require different tools, different metadata handling, different authentication questions, and different ways of linking an item to a person, a device, a location, or a time.

The categories reported publicly include an iPhone extraction, text exchanges, Uber records, Amazon purchases, Home Depot Postmates delivery logs, surveillance video involving the defendant’s Tesla, and other digital or transactional evidence.[2][5][6] Some of those categories are more sensitive than others, and the factual allegations in the case are grave. But for discovery management, the relevant point is the variety of source systems. The defense is not reviewing “messages” or “videos” in the abstract. It is trying to understand how each item was collected, what metadata came with it, what may be missing, and how the prosecution plans to sequence it into a coherent theory.

• Device evidence may require forensic validation, extraction reports, hash values, and attention to user attribution.
• Cloud evidence may arrive through provider exports, account records, synced files, or messages detached from the original device context.
• Transactional records may be structured but still need identity, timing, payment, account, and delivery-location analysis.
• Video evidence may consume disproportionate storage while requiring time-coded review rather than ordinary document coding.
• Wiretap-derived material adds its own chain of authorization, minimization, logging, and relevance questions.

The wiretap piece is especially easy to understate. Law Commentary reported that a wiretap was authorized during the investigation.[5] In discovery terms, that can mean more than recordings or transcripts. It can involve application materials, orders, returns, logs, minimization records, metadata, and challenges over what was captured and how. Even if only a portion becomes central at a preliminary hearing, the defense still has to decide what to inspect before conceding that the prosecution’s presentation is complete enough to proceed.

The grand juries point to an evidence-gathering case before indictment

One of the more revealing details is that three investigative grand juries were used in November, December, and February, according to Courthouse News.[2] The reported point was not that those grand juries returned an indictment. They were used to gather evidence.

That posture helps explain how a preliminary hearing could arrive with so much already accumulated and so much still unresolved for production. Investigative grand juries can generate testimony, records, subpoenas, and leads that then point investigators toward additional accounts, devices, service providers, and business records. Each new source may be manageable in isolation. Together, they create the kind of layered record that is difficult to hand over, process, and understand on a conventional preliminary-hearing schedule.

This is where the public case file becomes more useful than broad claims about criminal evidence “going digital.” A general industry statistic would not add much here, especially if its origin is unclear. The better lesson comes from the docket facts themselves: three investigative grand juries, a wiretap, device and cloud material, transactional records, video, and a production percentage that gave the defense a concrete readiness argument before the court ever reached trial management.[2][3][5]

Why partial production is different in a criminal case

In a civil document review, a producing party may stage production and the receiving party may build review workflows around rolling batches. There can be fights over custodians, search terms, privilege logs, and format, but both sides generally understand that production and review will proceed over time. Criminal discovery has different pressure points.

The state controls the investigation before charging. It often has the first look at seized devices, provider returns, surveillance footage, and law-enforcement analyses. The defense receives that record later and must make decisions under dates set by the court. When only about 30% has been turned over shortly before a scheduled preliminary hearing, the defense’s problem is not simply that its reviewers have a long queue. The problem is that the missing 70% may change which witnesses matter, which factual assumptions are safe, and which prosecution claims deserve attack.[3]

The imbalance is also practical. Prosecutors may have teams of investigators, analysts, agency contacts, and service-provider records flowing through channels already familiar to them. Defense counsel must receive, index, search, de-duplicate where possible, preserve forensic context, and translate that mass into litigation decisions. In a capital case, the tolerance for rushing that process should be low.

None of that means the defense gets an open-ended veto over the calendar. Judges still have to manage witness availability, public interest, victim-family interests, jail status, and the prosecution’s obligation to move a serious case forward. But a judge facing an incomplete production record has fewer clean options. Pushing ahead risks making the probable-cause hearing look procedurally thin. Continuing the hearing rewards delay, whether or not counsel intended delay as a tactic.

The prosecution’s burden is not only to possess evidence, but to make it usable

The Los Angeles County District Attorney’s Office announced the capital murder charge against D4vd, whose legal name has been reported as David Anthony Burke, in the killing of 14-year-old Celeste Rivas Hernandez.[7] The charge sets the stakes, but it does not solve the mechanics. A prosecutor can believe the evidence is strong and still face a discovery system that cannot move 40-plus terabytes into defense-usable form quickly enough for the first contested evidentiary hearing.

Possession is not production. Production is not review. Review is not comprehension. And comprehension is not courtroom use. Those distinctions are sometimes treated as legal-technology housekeeping until a hearing date exposes them.

The prosecution’s practical challenge is to decide what the defense must receive, in what form, with what indexes or load files, and with what explanation of origin. A giant undifferentiated transfer may satisfy neither fairness nor efficiency if the receiving side cannot tell which materials came from which device, account, warrant, subpoena, grand-jury return, or investigative step. At the same time, prosecutors cannot wait for a perfect review environment before asking a court to hold a preliminary hearing in a charged homicide case.

That tension is why the D4vd record is more instructive than the celebrity coverage around it. The procedural problem would look familiar in a non-famous case: the state has built an evidence-heavy prosecution; the defense says it cannot responsibly test the case without more production and review time; the court has to decide whether the calendar belongs to the legal standard or to the mechanics of digital discovery.

A public window created by a sealing fight

The public knows as much as it does partly because the defense sought to seal a prosecution evidence brief and the court denied that request, leaving a 9-page prosecution filing public.[6] That is a narrow procedural fact, but it explains the unusual visibility into a preliminary-hearing record that might otherwise have remained largely opaque.

The denial also created an uneasy reporting environment. Public filings may contain allegations that are highly prejudicial and not yet tested at trial. They may also contain precisely the operational details—volume, source categories, investigative sequence—that lawyers and discovery professionals need in order to understand how the case is functioning. The useful path is not to ignore the filing, and not to turn it into spectacle. It is to read it as a procedural artifact.

Other courtroom positioning has continued alongside the discovery fight. NBC Los Angeles reported that the defense requested that D4vd appear without handcuffs at the preliminary hearing, citing standards governing courtroom restraints.[8] That motion may matter to courtroom presentation, but it is not the force shaping the case schedule. The repeated continuances and the production record are doing that work.

The defense delay lever is structural, not mysterious

There is no need to romanticize the defense posture to see its leverage. A party that has received only a minority of a massive discovery set can ask for more time without sounding evasive. The larger and more heterogeneous the record, the harder it is for the prosecution to answer that request with a simple claim that counsel should have been ready.

The leverage comes from the structure of the case. If the prosecution’s theory depends on connecting devices, cloud accounts, transactional records, delivery logs, location evidence, surveillance, and communications, the defense can argue that it needs to test the connections rather than review isolated excerpts. A damaging message may mean one thing if it is reliably tied to a device and time. It may mean another if account access, synchronization, deletion, or context is disputed. A purchase record may look incriminating only if identity, timing, delivery, and surrounding conduct all hold together.

That is the responsible version of the defense argument. The strategic version is that every continuance buys time. Both can be true. Due process and tactical advantage are not opposites in a discovery-heavy criminal case; they often travel in the same motion.

For prosecutors, that dual reality is frustrating because it can make diligent investigation look like delay-causing overcollection. For judges, it creates a management problem that does not fit neatly into ordinary readiness questions. For defense counsel, it supplies the rare continuance request that sounds less like calendar preference and more like professional obligation.

What the July 21 hearing can and cannot answer

The preliminary hearing that began July 21 is designed to address whether the prosecution has enough evidence to proceed, not whether the discovery system has solved every downstream review problem.[1] A judge could hear a focused presentation and still leave major disputes for later. The hearing may clarify parts of the prosecution’s theory, but it will not necessarily reveal whether the defense has mastered the full 40-plus-terabyte environment.

That limitation is important. One capital case involving a famous defendant should not be turned into a universal rule about every digital-evidence prosecution. The public record does not support a clean conclusion that all modern criminal cases will be controlled by terabyte-scale discovery, or that defense continuance motions in such cases are always justified.

It does support a narrower and more useful conclusion. In this prosecution, evidence volume became a case-management fact before trial. The 40-plus-terabyte disclosure, the roughly 3 terabytes of iCloud material, the three investigative grand juries, the wiretap, the mixed categories of device, cloud, transactional, delivery, and video evidence, and the report that only about 30% had been turned over by April 23 all helped shape the path from May 1 to July 21.[2][3][5]

That is the procedural shift the record supports. In digital-heavy criminal litigation, evidence volume can become as consequential as many substantive disputes, especially before trial, when the defense is still trying to learn the record and the court is being asked to keep the case moving anyway.

References

1. Judge to Hear Evidence Against Singer D4vd in Killing, Dismemberment of Teen and Decide on Trial — US News — https://www.usnews.com/news/entertainment/articles/2026-07-21/judge-to-hear-evidence-against-singer-d4vd-in-killing-dismemberment-of-teen-and-decide-on-trial
2. Prosecutors detail grisly evidence in murder case against musician D4vd — Courthouse News — https://www.courthousenews.com/prosecutors-detail-grisly-evidence-in-murder-case-against-musician-d4vd/
3. Singer D4vd's preliminary hearing set for July 21 in killing of 14-year-old Celeste Rivas Hernandez — ABC7 — https://abc7.com/post/singer-d4vd-due-back-court-killing-14-year-old-celeste-rivas-hernandez/19463768/
4. D4vd Hearing Delayed Again After DA Released Chilling Evidence Claims — Rolling Stone — https://www.rollingstone.com/music/music-news/d4vd-hearing-delayed-month-da-evidence-claims-1235561278/
5. Prosecutors Cite Digital Evidence as Murder Case Against D4vd Moves Toward Preliminary Hearing — Law Commentary — https://www.lawcommentary.com/articles/prosecutors-cite-digital-evidence-as-murder-case-against-d4vd-moves-toward-preliminary-hearing
6. More details about evidence in D4vd murder case revealed — NBC Los Angeles — https://www.nbclosangeles.com/news/local/d4vd-court-hearing-celeste-rivas-hernandez-murder-2/3883185/
7. Singer D4vd Charged With Capital Murder of 14-Year-Old Girl — LA County DA — https://da.lacounty.gov/about/inside-LADA/singer-d4vd-charged-capital-murder-14-year-old-girl
8. Singer D4vd requests handcuffs off for preliminary hearing in murder case — NBC Los Angeles — https://www.nbclosangeles.com/investigations/d4vd-wants-cuffs-off-for-preliminary-hearing/3919498/