Short answer: The federal rule that decides whether a recording counts as what somebody says it is has ten example routes, and the one covering anything a machine made does not ask about the file at all. It asks for a description of the process that produced it. Two 2017 paragraphs let that description arrive as a signed certification instead of a live witness, and the committee note attached to them is unusually frank about how little a certification buys. None of this turns a home camera into an exhibit. What it does is spell out, in public, which facts about an unattended arrangement somebody else would need in order to argue with it.
The committee that wrote the rule reached for an X-ray to explain it. That choice is the whole idea in one image: nobody watched the inside of the patient, so the picture is not trusted because a witness vouches for it. It is trusted because the machine and the procedure are trusted. Swap in a phone on a shelf pointed at an empty hallway and the structure is identical — no one saw the hallway — which moves the question off the picture and onto the arrangement that made it.
The sentence the whole thing rests on
Authentication in the federal system is a threshold, and the general statement in Rule 901. Authenticating or Identifying Evidence is short enough to quote whole:
"the proponent must produce evidence sufficient to support a finding that the item is what the proponent claims it is"
Note what is being asked for. Not certainty, not a forensic report, not an unbroken chain of hands. Evidence sufficient to support a finding — enough for a reasonable person to conclude the thing is what you say it is. The rule then gives examples, and says in its own text that they are "examples only — not a complete list". The first is the ordinary route: somebody with knowledge testifies that the item is what it is claimed to be.
The ninth is the one that covers anything a machine made:
"Evidence describing a process or system and showing that it produces an accurate result."
The Advisory Committee note explains the reasoning without any hedging at all:
"Example (9) is designed for situations in which the accuracy of a result is dependent upon a process or system which produces it. X-rays afford a familiar instance."
The route that does look at the file
It would overstate things to say the rule never looks at the artefact. Example (4) does, and it is worth quoting because of how it ends:
"The appearance, contents, substance, internal patterns, or other distinctive characteristics of the item, taken together with all the circumstances."
Taken together with all the circumstances. Even the route that examines the thing itself is anchored to what surrounded it. Example (8), for old material, wants a document to have been "in a place where, if authentic, it would likely be" — place again, not pixels. Across the list, the properties of the file are rarely asked to carry the weight alone, and for a machine-made recording example (9) does not ask about them at all.
The ceiling, stated up front
It would be easy to read the above as a route to getting home footage used, so here is the limit in the rule-makers' own words, from the same page:
"compliance with requirements of authentication or identification by no means assures admission of an item into evidence, as other bars, hearsay for example, may remain"
Authentication is a gate, and past it are more gates. The committee note to the 2017 amendments makes the same point with a concrete case, and it is a better illustration than any abstraction: a plaintiff offers a printout of a web page carrying a defamatory statement, along with a certification describing how the page was retrieved. "Even if that certification sufficiently establishes that the webpage is authentic, defendant remains free to object that the statement on the webpage was not placed there by defendant."
The mechanism was verified. Who did the thing was not. Whether a recording is relevant, whether it is hearsay, whether it survives a specific objection in a specific proceeding — none of that is touched by anything in this post.
Where a description can stand in for a person
Two paragraphs were added in 2017 to save parties the cost of flying in a witness whose testimony nobody actually disputes. From Rule 902. Evidence That Is Self-Authenticating, the first of them covers outputs:
"A record generated by an electronic process or system that produces an accurate result, as shown by a certification of a qualified person that complies with the certification requirements of Rule 902(11) or (12)."
The accompanying note ties it back to the example above in one sentence:
"The Rule specifically allows the authenticity foundation that satisfies Rule 901(b)(9) to be established by a certification rather than the testimony of a live witness."
The same foundation is wanted either way. What changed is who may deliver it. The second paragraph handles copies rather than outputs:
"Data copied from an electronic device, storage medium, or file, if authenticated by a process of digital identification, as shown by a certification of a qualified person"
The phrase to sit with is a process of digital identification. That is the requirement. Hashing is the example the committee gives — "A hash value is a number that is often represented as a sequence of characters and is produced by an algorithm based upon the digital contents of a drive, medium, or file" — but the note is careful to add that the rule "is flexible enough to allow certifications through processes other than comparison of hash value, including by other reliable means of identification provided by future technology." Requirement first, technique second, and the order is deliberate.
The same note is candid about how much a certification buys you:
"the authentication establishes only that the output came from the computer"
That is a useful sentence to keep next to any claim about verified video. Establishing that a file came out of a particular system says nothing about whether the system was pointed at anything worth seeing.
What that description contains for a phone on a shelf
Here is where this stops being about courts. The rule describes a class of facts, and that class is knowable to the person who set the thing up and to almost nobody else. Each of these takes a couple of minutes while the arrangement is running and is guesswork a year later.
The device, named specifically. Manufacturer, model, and the software version it was on. A phone kept as a camera is usually an old phone, and old phones get described later as the spare Samsung, which is not a way to tell one handset from another.
The software and its version. Which application, which version, and where it came from. Applications update themselves; the version that made a file in March may be gone by autumn.
The settings that shape the output. Resolution, frame rate, whether audio was being captured, whether footage was written in segments and how long a segment ran, and what happened when storage filled. Every one of those changes what a file contains and what its gaps mean.
Where the clock came from. A recording's stated time is the device's belief about the time. Whether that belief was set by hand or by the network is a fact about the process, and it is the kind of thing an opponent asks about first.
What the camera could see. Where the phone sat, what direction it faced, what was outside the frame, and what the lighting was. This is the part people assume is obvious from the footage. It is obvious to the person who mounted it and to no one else.
How files got from the phone to wherever they are now. Copied over the network, pulled over a cable, synced by something. If a copy is what exists, the identification paragraph above is about exactly this step.
Written down, that is a page. Reconstructed from memory eight months later, it is a series of shrugs, and the shrugs are load-bearing: a description that cannot say what the frame excluded is a description that cannot rule anything out.
Who the description is actually for
The easy reading of all this is that the description is yours — something you assemble to make your footage count. The committee note points somewhere less flattering. Both 2017 paragraphs carry a notice requirement, and the note explains what the notice is for:
"A challenge to the authenticity of electronic evidence may require technical information about the system or process at issue, including possibly retaining a forensic technical expert; such factors will affect whether the opponent has a fair opportunity to challenge the evidence given the notice provided."
The description is written so the other side can attack it. That is its function. A certification is not a claim the process was good; it is a disclosure of what the process was, handed over early enough that somebody hostile has time to find the hole in it.
Which is the part worth borrowing, because it inverts the instinct. The reason to write down that the phone faced the gate rather than the driveway is not that it strengthens your account. It is that it is the sentence somebody can check.
What this post does not cover
I am not a lawyer and nothing here is advice about any situation. Three limits worth stating plainly.
These are the federal rules, governing proceedings in United States federal courts. Many state codes are modelled on them and many are not, and the pages linked above carry the federal text and nothing about who else adopted it. If this matters to you, the rules of the place you are in are the ones to read.
Who counts as a qualified person for one of those certifications is not answered on either page. The rules set out a procedure and a notice requirement; the qualification is decided elsewhere. Writing careful notes about your own setup does not make anybody a qualified person and does not produce a certification.
Whether any of this would ever be applied to a household recording is not something the rule text can tell you, and I have no data on how often it happens. What I can say is that the description the rule asks for is the same description that answers an insurer, a landlord, a neighbour, or your own memory in a year, and it costs the same either way.
The part that is not about courts
What is striking about the ninth example is how ordinary its demand is. It does not ask for tamper-proof hardware or a trusted third party. It asks somebody to describe how the thing works and to show that it works accurately — which is, in different words, the question a careful person would ask about any machine nobody is standing next to.
And the committee's word for what the notice buys is not proof. It is challenge. A description of your setup does not settle anything; it gives somebody a specific thing to disagree with. An account nobody can disagree with is not a strong account — it is one that cannot be tested, which is worth about the same from you as from anybody else. Eight months on, that is the difference between a page you can hand over and a shrug.
Try it: Background Camera RemoteStream on Google Play — record with the screen off, keep footage on the device, watch it over your own network.
Sources, all first-party, read on 2026-09-08:
- Rule 901. Authenticating or Identifying Evidence — rule text and Notes of Advisory Committee on Proposed Rules
- Rule 902. Evidence That Is Self-Authenticating — rule text, paragraphs (13) and (14), and the Committee Notes on Rules—2017 Amendment
Both as published by the Legal Information Institute at Cornell Law School. Every quotation above is verbatim rule text or an official committee note, linked at the point of use.
Top comments (0)