How to Authenticate WhatsApp Screenshots for Court Submission in India (2026 Guide)

Home › Blog › Authenticate WhatsApp Screenshots for Court

Table of Contents

1. Quick Answer: Are Raw WhatsApp Screenshots Admissible Without Verification?
2. The Legal Trap: Why Courts Dismiss Screenshots Every Day
3. Section 63 BSA 2023: The Statutory Requirements Explained
4. The Supreme Court's Rulebook: Anvar, Shafhi, and Arjun Panditrao
5. Delhi High Court on Screenshot Rejection: Dell v. Adeel Feroze
6. The 7-Step Forensic Authentication Protocol
7. SHA-256 Hash Validation: Your Mathematical Alibi
8. Cropped Screenshot vs Forensic Chronological PDF: Comparison Matrix
9. Case Study: How a ₹2 Crore Recovery Turned on One Screenshot
10. Cross-Examination Checklist: The 8 Questions Opposing Counsel Will Ask
11. Section 63 BSA Certificate Drafting Template
12. Court Filing Checklist: From PDF to Exhibit Marking
13. 7 Fatal Mistakes That Get Screenshot Evidence Rejected
14. Frequently Asked Questions
15. Conclusion & Action Plan

Quick Answer: Are Raw WhatsApp Screenshots Admissible Without Verification?

No — not reliably. A raw, cropped WhatsApp screenshot without a certificate under Section 63 of the Bharatiya Sakshya Adhiniyam (BSA), 2023 (the successor to Section 65B of the Indian Evidence Act, 1872) can be legally rejected, and Indian courts reject them daily.

Here is the position in one paragraph, so you can act immediately:

The only screenshots that survive cross-examination are those backed by four pillars: (1) a full chat export — not cropped images, (2) a cryptographic SHA-256 integrity hash generated at capture time, (3) a properly drafted Section 63 BSA certificate, and (4) the ability to produce the original device on request.

The Legal Trap: Why Courts Dismiss Screenshots Every Day

Every week, litigants across India lose cases — or settle for a fraction of what they're owed — because the judge rules their WhatsApp screenshots inadmissible. The pattern is so common it has a name among trial lawyers: "the screenshot ambush."

Here is exactly how it plays out in a real cross-examination:

1. You file your printouts of WhatsApp screenshots showing the other party admitting they owe you ₹4,80,000.
2. The opposing counsel objects: "My Lord, these are unverified screenshots. They could be fabricated in Photoshop or one of the many fake WhatsApp generator apps available online. There is no certificate under Section 63 BSA."
3. The judge asks you one question: "Can you produce the certificate, or the original phone with this chat?"
4. If your answer is no, the evidence is excluded — and the admission that would have won your case is legally invisible.

This is not a hypothetical risk. It is the default outcome of walking into an Indian courtroom with bare screenshots in 2026, because:

Why screenshots are uniquely vulnerable to challenge

The fix is not complicated. It requires converting your screenshots from pixels into a statutorily certified, hash-verified, chronological record. That is exactly what the rest of this guide walks you through.

Section 63 BSA 2023: The Statutory Requirements Explained

On 1 July 2024, the Indian Evidence Act, 1872 was repealed and replaced by the Bharatiya Sakshya Adhiniyam (BSA), 2023. The section that governs your WhatsApp screenshot is now Section 63 BSA — the direct successor to Section 65B.

Section 63(4) BSA — the certificate, decoded

Section 63(4) requires that a certificate be submitted along with the electronic record at each instance where it is submitted for admission. The certificate must do four things:

It is sufficient for these matters to be stated to the best of the certifier's knowledge and belief — a standard carried over from Arjun Panditrao.

The old law vs the new law — quick reference

The Supreme Court's Rulebook: Anvar, Shafhi, and Arjun Panditrao

Three Supreme Court judgments form the complete rulebook for authenticating your WhatsApp screenshots. Understanding the sequence matters, because many litigants (and even junior advocates) are still quoting the overruled case.

1. Anvar P.V. v. P.K. Basheer (2014) 10 SCC 473 — the foundation

An election petition challenged the use of uncertified CDs. A three-judge bench held:

• Sections 65A and 65B are a complete code for electronic evidence; the general secondary-evidence route (Sections 63/65 IEA) does not apply to electronic records.
• A Section 65B(4) certificate is mandatory for secondary electronic evidence.
• The earlier relaxed position in State (NCT of Delhi) v. Navjot Sandhu (the Parliament attack case, 2005) was overruled.

2. Shafhi Mohammad v. State of Himachal Pradesh (2018) 2 SCC 801 — the detour

A two-judge bench "clarified" that the certificate requirement was procedural, not mandatory, and could be relaxed where a party didn't possess the device. Litigants began relying on this to skip certification. This was a trap.

3. Arjun Panditrao Khotkar v. Kailash Kushanrao Gorantyal (2020) 7 SCC 1 — the final word

A three-judge bench settled the conflict decisively. This is the controlling law today:

1. The certificate is a condition precedent to admissibility. Shafhi Mohammad did not state the law correctly and is overruled.
2. Oral evidence cannot substitute for the certificate — "to hold otherwise would render Section 65B(4) otiose."
3. If the original device is produced — you step into the witness box and prove the phone on which the chat is stored is owned/operated by you — no certificate is needed. The device itself is primary evidence.
4. If you cannot produce the device (the normal situation — nobody hands their phone to the court file), your only route is a certified record under Section 65B(1) (now 63 BSA) with the certificate.
5. If a third party in control of the device refuses to certify, you may apply to the court under lex non cogit ad impossibilia (the law does not demand the impossible) — but this is a remedy of last resort, not a strategy. Courts expect you to certify your own device records.
6. Where a defective certificate was filed or a demanded certificate was refused, the trial judge must summon the certifying person — but as the Court warned, "electronic records being more susceptible to tampering, alteration, transposition, excision... without such safeguards, the whole trial... can lead to travesty of justice."

Delhi High Court on Screenshot Rejection: Dell v. Adeel Feroze

In Dell International Services India Pvt. Ltd. v. Adeel Feroze (2024:DHC:4954), Justice Subramonium Prasad dealt with exactly your situation. Dell submitted a screenshot of a WhatsApp conversation to support its procedural defense before the Consumer Commission. The Delhi High Court refused to look at it:

Three lessons from this 2024 judgment:

1. Even large corporates with law firms lose this battle. Dell had professional representation and still filed an uncertified screenshot. Don't assume sophistication equals admissibility.
2. "It was only for a procedural point" is not an exception. The court refused to consider the screenshot at all, for any purpose, without certification.
3. The objection can be raised at any stage — the later you file your certificate, the more it looks like an afterthought manufactured under litigation pressure.

The Punjab and Haryana High Court said the same thing even more bluntly in Rakesh Kumar Singla v. Union of India (2021): certification for WhatsApp messages is mandatory, and messages are admissible only after due compliance.

The 7-Step Forensic Authentication Protocol

This is the exact sequence used by litigants whose screenshot evidence survives cross-examination. Follow it in order — skipping steps is what gets evidence rejected.

Step 1 — Secure the device before anything else

The moment litigation becomes likely, treat your phone as evidence:

• Enable Airplane mode before opening the chat (prevents the counterparty's "Delete for Everyone" from syncing to your device).
• Disable auto-backup sync temporarily — a Google Drive/iCloud restore can overwrite historical message states.
• Photograph the phone showing the chat with the phone's own clock/status bar visible — a spontaneous capture contemporaneous with discovery.
• Record the device particulars now: make, model, OS version, IMEI (dial *#06#), and your SIM number. You'll need these for the certificate.

Step 2 — Export the full chat with media (never crop)

In WhatsApp: chat → ⋮ → More → Export chat → Include Media.

• Cropped screenshots are evidence-weak (see the comparison matrix below). The native export produces the complete _chat.txt file with every message, timestamp, and media reference in sequence.
• The export goes up to ~10,000 messages with media / 40,000 without — sufficient for virtually all disputes. If your chat exceeds this, export in dated segments and preserve all segments.
• Transfer the ZIP to your computer via USB cable or local sharing — not through another cloud app that re-compresses files.

Step 3 — Generate the SHA-256 integrity hash immediately

Hash the exported ZIP (and later the final PDF) at the moment of creation:

• Windows: right-click → CRC SHA → SHA-256 (via 7-Zip), or certutil -hashfile file.zip SHA256 in Command Prompt.
• Mac/Linux: shasum -a 256 file.zip
• Record the hash in writing (notebook + photo + email it to yourself). The email timestamp becomes your proof of when the file existed in this exact state.

This hash is your mathematical alibi: any future accusation of editing can be disproven in one line of computation.

Step 4 — Convert to a chronological court-format PDF

Registry clerks and judges reject messy exhibits. Your PDF must have:

• Chronological message order with date/time stamps on every message
• Phone numbers (+91 format), not just contact names — names are changeable; numbers are legally attributable
• Media embedded inline at the position where it appeared in the conversation
• Continuous pagination with a running exhibit label (e.g., "Exhibit C-1, Page 14 of 67")
• Language preserved — if the chat is in Hindi or a regional language, do not machine-translate the evidence itself; provide translation as a separate annexure

Step 5 — Draft the Section 63 BSA certificate

Use the full four-limb certificate (template provided in Section 11). The certificate is filed with the record — "at each instance where it is being submitted for admission" under Section 63(4). File it with your plaint/complaint/affidavit, not as an afterthought.

Step 6 — Prepare your oral foundation

Even with a perfect certificate, you should be ready to testify:

• You operated the device; the number is registered to you (carry the SIM registration/CAF proof or a recent bill showing your number).
• You exported the chat yourself on [date], using WhatsApp's export function.
• The hash was generated at export; the PDF filed matches that hash (produce the hash verification on request).
• You have not edited, deleted, or reordered any message.

Step 7 — File with a sealed digital copy

Alongside the printout/PDF:

• Burn the original export ZIP + PDF + hash record to a write-once CD-R or sealed USB drive, labeled as an exhibit.
• This satisfies the storage-media limb and gives the court (and opposing forensic examiner, if ordered) the source file to verify your hash against.

SHA-256 Hash Validation: Your Mathematical Alibi

Of everything in this guide, the SHA-256 hash is the single element most litigants skip — and the single element that most terrifies opposing counsel, because it converts a shouting match about "fake screenshots" into arithmetic.

What SHA-256 actually is (in plain language)

SHA-256 is a cryptographic algorithm that takes any file — your 200 MB WhatsApp export ZIP or your 67-page PDF — and produces a unique 64-character fingerprint. Two properties make it decisive in court:

1. Avalanche effect: Change even one pixel or one character in the file, and the fingerprint changes completely and unpredictably. There is no "slight edit" that keeps the same hash.
2. One-way function: You cannot reverse-engineer the file from the fingerprint, and you cannot craft a different file that produces the same fingerprint (practically impossible — the search space is 2^256).

How the hash wins arguments

The verification ritual (do this in court if challenged)

1. Open Terminal (Mac/Linux) or Command Prompt (Windows).
2. Run the hash command on the filed file: shasum -a 256 exhibit-c1.pdf or certutil -hashfile exhibit-c1.pdf SHA256.
3. Compare the output, character for character, with the hash in your certificate and your pre-litigation email.
4. A match is conclusive proof of integrity since capture.

Cropped Screenshot vs Forensic Chronological PDF: Comparison Matrix

The conclusion is not that screenshots are useless — it's that a screenshot's only safe role is as a supplementary pointer to the certified chronological record, never as the primary exhibit itself.

Case Study: How a ₹2 Crore Recovery Turned on One Screenshot

A composite case study based on a common commercial-dispute pattern in Delhi courts. Names changed; the legal mechanics are exactly as described.

The dispute: Rohan Mehta (Delhi, textile trader) supplied goods worth ₹2.04 crore to a buyer over 14 months. Payment stopped. The buyer's director had — on WhatsApp — repeatedly confirmed balances, promised payment dates, and once sent a voice note saying "bhai 2 crore ka figure sahi hai, October mein clear kar dunga." When sued, the buyer's counsel raised the standard defense: fabricated chats.

What Rohan had done right (before reading any guide — pure instinct):

1. When the first payment bounced, he exported the full business chat with media and saved the ZIP to his laptop the same evening.
2. He had his CA email the ZIP to himself and the CA — creating a third-party timestamped record of the file's existence.
3. He kept the original phone untouched — no factory reset, no WhatsApp reinstall.

What he had done wrong:

• He had no hash and no certificate. His advocate filed 40 pages of screenshot printouts.

The ambush: At trial, opposing counsel objected under Section 63 BSA: no certificate, screenshots cropped, contact names not numbers, no integrity proof. The judge looked inclined to exclude. Rohan's case — with a written admission of debt — was about to be decimated by procedure.

The recovery (this is the part most articles skip):

• The advocate sought adjournment, then filed a proper Section 63 BSA certificate — the four-limb format — signed by Rohan as the person in charge of the device, with IMEI particulars.
• The original export ZIP was burned to a sealed CD; because the file had been preserved untouched since capture, the advocate generated the SHA-256 retroactively and proved via the CA's email (sent before the suit) that the file was identical.
• On the next date, the hash on the CD matched the hash in the certificate. The objection collapsed. The court admitted the chats, and — critically — the buyer never seriously contested the debt again. The admission of liability in writing settled the case: ₹1.7 crore recovered via consent decree within four months, versus a probable write-off.

The three transferable lessons:

1. The admission wins cases; the certificate gets the admission into evidence. Rohan's evidence was always strong. It only became usable after procedural compliance.
2. Preserve first, litigate later. The pre-suit CA email — done on instinct — became the timestamp anchor. Deliberate preservation beats instinct.
3. Retroactive hashing works only if the file was never touched. If Rohan had edited, re-saved, or re-compressed the ZIP even once, the hash would have changed and the timeline claim would have collapsed.

Cross-Examination Checklist: The 8 Questions Opposing Counsel Will Ask

If you are the witness authenticating the evidence, these are the standard attack lines. Prepare a one-line truthful answer for each before you enter the box. Your evidence file should contain the proof backing each answer.

Section 63 BSA Certificate Drafting Template

Copy this structure and fill in your particulars. It is drafted to satisfy all four limbs of Section 63(4) BSA and the Schedule format. Have your advocate review the final version for your specific forum.

CERTIFICATE UNDER SECTION 63(4) OF THE BHARATIYA SAKSHYA ADHINIYAM, 2023
[Certificate for Submission of Electronic Evidence — as per the Schedule to the BSA, Part A]

I, [FULL NAME], aged ___ years, son/daughter of [___], resident of [___], do hereby certify
to the best of my knowledge and belief, as follows:

1. IDENTIFICATION OF THE ELECTRONIC RECORD
   The electronic record accompanying this certificate is a true export of the WhatsApp
   conversation between mobile number +91-[YOUR NUMBER] (operated by me) and mobile
   number +91-[OTHER PARTY NUMBER], spanning messages dated [DD/MM/YYYY] to
   [DD/MM/YYYY], produced in the form of a chronological PDF of [__] pages ("the Record").

2. MANNER OF PRODUCTION
   The Record was produced by me on [DATE] using the native "Export Chat" function of the
   WhatsApp application (version ___), selecting "Include Media", on the device described
   below. The export file ([filename].zip) was converted to the accompanying PDF without
   alteration, addition, deletion, or reordering of any message, timestamp, or media item.

3. PARTICULARS OF THE DEVICE
   Device: [Make & Model, e.g., Samsung Galaxy S23]
   Operating System: [Android __ / iOS __]
   IMEI: [___]   (dial *#06# to confirm)
   SIM/Number: +91-[___]
   The said device was regularly used by me over the relevant period to store and process
   the information contained in the Record, in the ordinary course of my communications.

4. SECTION 63(2) CONDITIONS
   (a) The device was regularly used to store/process information of the kind contained in
       the Record, for activities regularly carried on by me;
   (b) The information was regularly fed into the device in the ordinary course of those
       activities (via the WhatsApp application and its servers);
   (c) Throughout the material period the device was operating properly, and any break in
       operation did not affect the Record or the accuracy of its contents;
   (d) The information contained in the Record is a true reproduction/derivation of the
       information so fed into the device.

5. INTEGRITY VERIFICATION
   The export file was hashed using SHA-256 on [DATE] at [TIME], producing the hash:
   [64-CHARACTER HASH]
   The accompanying PDF and sealed storage media bear the identical hash, verifiable at
   any time, and no alteration whatsoever has been made to the Record since hashing.

6. DECLARATION
   I declare that the contents of this certificate are true to the best of my knowledge and
   belief, and I am aware that I am liable to prosecution for any false statement herein.

   Verified at [City] on this [__] day of [Month], 2026.

   [SIGNATURE]
   [FULL NAME]
   [Address, Mobile Number, Email]

[Part B — Expert verification, where applicable: to be completed by the digital forensics
expert / tool operator confirming the hash computation and conversion process.]

Court Filing Checklist: From PDF to Exhibit Marking

Print this and tick it before you file. Every unchecked box is a rejection risk at the registry or an objection point in cross.

• ☐ Full export (with media) taken and ZIP preserved untouched on a dedicated folder/USB
• ☐ SHA-256 hash generated, recorded in writing, and emailed to self/third party (pre-suit wherever possible)
• ☐ PDF generated: chronological, +91 numbers visible, media inline, dates on every message
• ☐ Pagination: continuous page numbers, running header/footer with case-style exhibit label (e.g., "Ex. C-4 / Page __ of __")
• ☐ Section 63 BSA certificate completed on all four limbs + integrity hash paragraph, signed and dated
• ☐ Expert/Part B verification attached where used
• ☐ Sealed media: export ZIP + PDF burned to CD-R (or sealed USB), labeled with case number, date, and hash
• ☐ Annexure/index: one-page index listing exhibits, page ranges, and what each proves
• ☐ Oral foundation prepared: your 4-point testimony script rehearsed (ownership → export → hash → no editing)
• ☐ Device readiness: original phone charged, available, WhatsApp installed and chat intact — in case the court invokes Door A of Arjun Panditrao
• ☐ Number attribution file: SIM registration / CAF / recent bill linking your +91 number to you (and whatever public/contract documents link the other party's number to them)
• ☐ Translation annexure (if chat is in Hindi/regional language): certified translation as a separate annexure, never substituted into the original
• ☐ Copies: per your forum's rules — typically one for court, one per opposite party, one for your file

7 Fatal Mistakes That Get Screenshot Evidence Rejected

Every rejected exhibit we've analyzed fails on one of these seven. Some appear in this guide's checklist; they're repeated here because they're the statistical reasons evidence dies.

The Dell v. Adeel Feroze outcome. After Arjun Panditrao, this is the single most common reason for exclusion, and it is 100% avoidable. No certificate → no admissibility → your best evidence legally does not exist.

Any blog, advocate, or relative who tells you "certification is procedural and can be relaxed" is quoting the overruled 2018 position. The law since July 2020 is categorical: the certificate is mandatory.

Every edit destroys the integrity claim. Courts have seen enough selectively edited exhibits to treat any cropped screenshot as presumptively unreliable. Export the full chat or don't rely on it at all.

Evidence manufactured under litigation pressure is the easiest to attack. Pre-suit preservation — export, hash, email timestamp — is worth more than ten post-suit certificates. If you've already filed, preserve today; late but genuine beats never.

If the other party sends "Delete for Everyone," the message vanishes from your phone too. Litigation opponents routinely wipe chats the moment they sense a dispute. Preservation is a race — the protocol in Step 1 (airplane mode, disable sync, immediate export) exists because the first mover wins it.

"I certify this is true" certificates are rejected on sight. The certificate must identify the record, describe production, give device particulars, and address the Section 63(2) conditions. Use the template above; don't freestyle it.

"Rahul Sharma" is not a person in evidence law; +91-98XXXXXX10 is. Names in your phonebook are your own typing. The export file reveals the underlying number — and the number, tied to SIM registration, is what binds the message to the human.

Frequently Asked Questions

1. Are raw WhatsApp screenshots admissible in Indian courts without verification?

No. Without a certificate under Section 63 BSA 2023 (or Section 65B IEA for pre-transition matters), a bare screenshot is routinely rejected — the Delhi High Court confirmed this in Dell International Services v. Adeel Feroze (2024). Screenshot-only evidence, even if genuine, can be excluded on objection.

2. What is the difference between Section 65B and Section 63 BSA?

Section 65B of the Indian Evidence Act 1872 was replaced by Section 63 of the Bharatiya Sakshya Adhiniyam 2023, effective 1 July 2024. The substance is the same — a mandatory certificate for electronic records — but the BSA expands device definitions (smartphones, cloud, networked devices treated as one system) and introduces a standardized Schedule format with an expert element.

3. Can the other party's lawyer claim my screenshots are Photoshop or AI-generated?

Yes — and in 2026, they almost certainly will. Your answers are: (a) you rely on the full native export, not cropped images; (b) a SHA-256 hash generated at capture proves the file is untouched; (c) the certificate satisfies Section 63(4); and (d) the original device and sealed media are available for examination. A hash predating the litigation is the strongest single rebuttal.

4. Do I have to surrender my phone to the court?

No. Under Arjun Panditrao Khotkar (2020), producing the original device is one of only two routes — but the normal route is a certified record plus certificate, keeping your phone with you. You must, however, keep the phone intact and be ready to produce it if the court directs.

5. What if the chat is in Hindi or another regional language?

Preserve the original exactly as written — never translate the evidence itself. File the original-language export with a certified English translation as a separate annexure, clearly marked as a translation. Courts in most states accept Hindi originals; the translation is for the record and for appellate clarity.

6. The other party already deleted the messages from their phone. Does my copy still work?

Yes — your export is your record of the conversation as it existed on your device. Their deletion doesn't affect your copy. The cross-examination battle then shifts to attribution and integrity, which is exactly what your hash, certificate, and number-linked export are built to win.

7. Can I use WhatsApp Web printouts instead of phone export?

Possible but weaker. WhatsApp Web introduces an extra device and session into the chain, each of which opposing counsel can interrogate. A native phone export with device particulars (IMEI, OS) in the certificate is the cleanest evidentiary chain.

8. How long does the whole authentication process take?

Manually: export (10 min), hashing (5 min), certificate drafting with advocate review (1–3 days), PDF formatting (1–2 hours to days depending on chat length). Via Chat2Evidence: about 5 minutes for export → court-ready PDF → auto certificate → hash, with zero upload from your device.

9. Will the judge definitely admit my evidence if I follow this guide?

No honest guide can promise that — admission is always the court's call, and the other side can still contest weight (interpretation, completeness of context). What this guide guarantees is the elimination of the procedural grounds on which screenshots are most commonly excluded. Once admitted, the argument moves to merits, where a written admission is devastating.

10. Is a tool-generated certificate as valid as one drafted by my advocate?

The statute doesn't grade certificates by who drafted them — it checks whether the four limbs of Section 63(4) are satisfied and the signer is a person in charge of the device. A tool that generates the full-format certificate (with hash and expert verification chain) and keeps everything on your device satisfies this cleanly. Your advocate should still review forum-specific filing rules.

Conclusion & Action Plan

Raw WhatsApp screenshots are the weakest way to present the strongest evidence most litigants own. The fix is not a better screenshot — it is converting your chat into a certified, hashed, chronological record that survives the two doors of Arjun Panditrao Khotkar: proper certification, or device production on demand.

Your action plan, in order:

• Today (15 minutes): If any dispute is even possible, export the relevant chats with media, generate the SHA-256 hash, and email the hash to yourself and one trusted person. This single habit wins more cases than any argument.
• This week: Convert your exports into court-format PDFs with +91 numbers, pagination, and media inline. Draft your Section 63 BSA certificates using the template above.
• Before filing: Run the filing checklist end-to-end, rehearse your oral foundation, and prepare the sealed media.
• Ongoing: Preserve first, always. Every new threatening or admitting message gets exported and hashed the day you receive it.

Your three options

For the vast majority of civil, consumer, matrimonial, and cheque-bounce matters, Option 2 delivers Option 3-grade evidentiary hygiene at a price that doesn't require thinking twice.

Related Guides

• How to Export WhatsApp Chat for Court (Step-by-Step) — the native export walkthrough this article builds on
• WhatsApp Audio Transcripts & Voice Notes under Section 63 BSA — when the evidence is a voice note, not a screenshot
• Preserve WhatsApp Evidence Before Filing a Case — the emergency protocol if litigation is imminent
• Are WhatsApp Chats Valid in Court in India? — the full admissibility framework, criminal vs civil

Disclaimer: This guide is legal information, not legal advice, and does not create an advocate-client relationship. Statutes and case law are stated as of September 2026. Consult a qualified advocate for your specific matter.