Short answer
Screenshots, texts, emails, receipts, and account records can support a consumer complaint or court claim. They aren't automatically admissible, though. A business may accept a screenshot during a support review, while a court may ask you to show that the record is genuine, complete, relevant, and being used for a permitted purpose.
The process determines what matters most:
- A merchant or marketplace complaint follows the company's support, return, warranty, and appeal procedures.
- A card, bank, or payment-app dispute follows the provider's instructions and any rules that apply to that payment method.
- A lawsuit follows the evidence rules and procedures of the court hearing it. Federal Rule of Evidence 901 is one example; federal rules don't automatically govern state small-claims court.
- A regulatory complaint follows the agency's intake requirements. Your records can explain the problem, but filing a complaint doesn't guarantee a refund or a court judgment.
There isn't one nationwide rule that makes every digital record valid everywhere. Keep the original information, preserve its context, and send it through the right escalation route.
What "admissible evidence" means
"Evidence" and "admissible evidence" aren't interchangeable.
Evidence is information that helps show what happened. A delivery confirmation, customer-service message, invoice, or bank statement may all be evidence.
Authentication is the process of showing that an item is what you claim it is. Under Federal Rule of Evidence 901, the proponent must provide enough support for a finding that the item is genuine. A witness who knows how the record was received, account details, distinctive features of the conversation, or surrounding circumstances may help provide that foundation. Rule 901 gives examples; it isn't a single mandatory checklist for every exhibit.
Relevance asks whether the record makes an important fact more or less likely. A message about a delayed shipment may be relevant to a delivery dispute. An unrelated conversation probably won't be.
Hearsay is a different question. A message can be authentic and still raise a hearsay issue if you offer it to prove that everything it says is true. Showing where a record came from doesn't automatically establish the truth of each statement in it. Other evidence rules may provide an exception or otherwise affect whether the statement can be used.
A judge may also consider whether an exhibit is incomplete, misleading, unfairly prejudicial, or covered by another rule. A company, marketplace, or payment provider may use a simpler review standard than a court.
Identify the process before collecting your exhibits
| Situation | What usually controls | What to preserve |
|---|---|---|
| Complaint to a seller | The seller's terms, return policy, warranty, and support process | Order details, policy version, receipts, messages, and the remedy requested |
| Marketplace or platform appeal | The platform's appeal instructions and submission limits | Case number, listing, account details, messages, photos, and delivery records |
| Card, bank, or payment-app dispute | The provider's dispute process and any law that applies to that payment rail | Statement, transaction ID, merchant communications, cancellation request, and proof of delivery or non-delivery |
| State small-claims case | The state's court rules, filing requirements, and deadlines | Organized exhibits, original files, printed copies, and a clear timeline |
| Federal court case | Federal evidence rules and the judge's procedures | Authentication information, complete files, collection notes, and supporting witnesses |
A platform can accept a screenshot that a court would examine closely. The reverse can happen too: a court may accept a record after you provide a foundation that a customer-service representative never requested. Calling something a "2026 evidence standard" doesn't turn it into a rule for every consumer dispute.
Preserve digital records while you still have access
An account can be closed. A chat can disappear. A website can change. Save the material before one of those things happens.
Keep the source record
A screenshot shows what appeared on a screen, but it may not preserve the underlying data. When the service allows it:
- Download the complete email, including its headers, instead of keeping only an image.
- Export a text or chat thread using the service's available tools.
- Save the original receipt, invoice, PDF, photograph, and attachment.
- Keep the order page, account record, or webpage that gives the disputed statement its context.
- Don't rely only on a forwarded message or a cropped image.
If there is no export option, write down how you obtained the screenshot and keep the relevant account or device, if practical.
Show enough context
The disputed sentence may not tell the whole story. Preserve the details that connect it to you and to the transaction:
- Sender's name, email address, phone number, username, or account page
- Recipient or account involved
- Date and time shown by the service
- Messages immediately before and after the disputed statement
- Order, ticket, tracking, or transaction number
- Relevant links, attachments, images, terms, or policies
- Full webpage address when the record came from a website
A displayed timestamp supports your account of events, but it isn't conclusive by itself. Note the time zone if the timing could affect the dispute.
Keep a collection log
For each important file, make a short note identifying:
- What the file contains
- Where it came from
- Which account or device you used to obtain it
- The date and time you saved it
- Who saved it
- Whether it is an export, screenshot, original, or copy
Names such as 2026-03-04-order-4832-receipt.pdf are easier to work with than IMG_8472.png. Keep a backup in a secure location. The log won't guarantee that a court admits the record, but it gives you a clear account of the record's history.
Separate originals from working copies
Keep an untouched copy apart from any version you annotate, crop, or redact. Don't edit the only copy.
If you need to conceal an account number, address, or other sensitive information, make a redacted copy and retain the complete version securely. Send only the information the recipient needs. When you submit a file, save a copy of what you sent and proof of the submission date.
Pair digital records with other documents
A complaint is easier to follow when a message is tied to independent transaction records. Depending on the problem, include:
- Order confirmation
- Receipt or account statement
- Shipping or delivery notice
- Cancellation request
- Customer-service ticket
- Photograph showing the product's condition
- Written warranty or policy
- Notes identifying dates, names, and promised actions
These records can confirm the timing and transaction details if someone questions an isolated screenshot.
How to support the authenticity of a text or email
The question under Rule 901 isn't whether a screenshot looks polished. It's whether the available information supports your claim about what the record is.
You may be able to explain:
- How you received it. Your own testimony can describe the account or device you used, how the message appeared, and when you saved it.
- How it connects to the sender. An identifiable phone number, email address, username, order number, or account history may link the communication to the claimed sender.
- What makes the conversation distinctive. Private transaction details, references to earlier messages, and later conduct can provide useful surrounding circumstances.
- What the original service shows. A complete email, export, or provider record is generally more informative than an isolated image.
- Who else can explain the system. In a formal case, a witness or records custodian familiar with the system may describe how the record was created and stored.
The Duke Judicature explanation of electronic evidence discusses how source, surrounding circumstances, and foundation affect electronic communications.
A screenshot by itself doesn't establish that:
- The person using the account was the named individual
- The text wasn't altered before it was captured
- The sender's statement was truthful
- The image shows the complete conversation
- The message overrides a written contract or posted policy
Those limitations don't necessarily make the record worthless. They show where additional records or testimony may be useful.
Use the records in the right complaint process
Contact the business first
The FTC recommends explaining the problem to the business and stating the resolution you want. Its guidance on solving problems with a business and its sample complaint letter can help you organize a written request.
A short timeline usually works better than a large unorganized attachment bundle. Include:
- Purchase or agreement date
- What the seller promised
- What went wrong
- When you notified the business
- What the business said or did
- The specific remedy you want
Attach copies, not irreplaceable originals. Label them plainly, such as "Exhibit A: order confirmation" and "Exhibit B: chat dated March 4." If you submit an online complaint form, save what you wrote and the screen confirming submission before you leave the page.
Keep notes about calls, including the representative's name, the date, and any promised follow-up.
Use the payment or platform procedure
For a card charge, bank transfer, debit transaction, prepaid account, or payment app, follow that provider's stated dispute process. Your evidence supports the explanation, but it doesn't replace a required notice, form, or deadline.
If a marketplace or platform has an appeal button, use it before its stated deadline. Keep the case number, the submission confirmation, and the response. Preserve the listing, relevant messages, photos, and delivery information as well.
A chat message from a merchant may help show what was represented, but it doesn't automatically guarantee a refund. The purchase terms, the payment method, the timing, and the provider's process may also affect the outcome.
Consider a court or regulator
If you are considering small claims, check the applicable state court's filing rules, evidence instructions, hearing date, and service requirements. Ask the clerk about exhibit formatting and copies, but don't expect the clerk to decide whether the evidence proves your case.
For a regulator or consumer-protection agency, follow its intake instructions and describe the facts concisely. An agency complaint may help identify a pattern or prompt a response. It isn't a substitute for a private lawsuit or a payment dispute.
Do hashes, blockchain, or AI make a record valid?
Technical tools can help document a file's history, but they don't answer every legal question.
- A hash can help show that a digital file has remained unchanged since the hash was calculated. It doesn't by itself prove who created the file, whether the source information was accurate, or whether the file was altered before the hash was made.
- A blockchain entry may help show that data was recorded at a particular time. It doesn't automatically prove the identity of a wallet holder, ownership of an asset, or the truth of the information entered.
- An AI-generated summary or image may leave out the original conversation or transaction. Keep the underlying messages, files, prompts, and system records rather than relying only on the AI output.
For an ordinary customer complaint, a readable timeline and complete transaction records may be more useful than a complicated technical process. If the dispute is high-value or likely to reach court, ask a qualified attorney or digital-forensics professional what preservation method fits the situation.
Consumer evidence checklist
Before sending a complaint or filing a dispute, check that you have:
- [ ] Receipt, invoice, or account statement
- [ ] Complete copy of the relevant messages or emails
- [ ] Screenshots showing sender, date, time, and surrounding context
- [ ] Order, case, tracking, or transaction number
- [ ] Applicable policy, warranty, or contract
- [ ] Dated timeline of events
- [ ] Notes of calls, including names and promised follow-up
- [ ] Untouched copy and separate redacted copy, if needed
- [ ] Proof of your complaint and the business's response
- [ ] Correct appeal, payment-dispute, court, or agency instructions
Common questions
Are screenshots automatically admissible in court?
No. The court may require authentication, relevance, context, and compliance with other evidence rules. The answer may differ between federal court, state court, arbitration, and an informal company review.
Can I use a text message from a business as proof of a promise?
Possibly. Preserve the full thread, identify the sender, and connect the message to your transaction. Check whether the statement was conditional, general, or limited by written terms.
Should I send my only original file to the company?
Usually, keep the original and send a copy unless the recipient has a documented reason to request the original. Save proof of what you submitted and when.
Does a timestamp prove that a screenshot is genuine?
No. It can support your account of events, but the source, surrounding messages, account details, and other records may matter as well.
What if the account or message was deleted?
Keep any copy you already have and record when and how you obtained it. Save related emails, notifications, invoices, and account records. If the dispute is significant, get advice promptly about preserving or requesting additional records.
This is general information for U.S. consumers, not legal advice. Before you contact the business or payment provider, export the complete conversation, save the transaction records, and write the timeline while the details are still available.