Blog Details

Introduction

Screenshots are the most common form of digital evidence people try to bring to court — a snap of a chat, a UPI or payment confirmation, a social-media post, a web page. They are also the weakest. A screenshot is just a picture of a screen: it can be cropped, edited or fabricated in seconds, and it carries no built-in proof of where it came from or that it has not been altered. This is a how-to and a cautionary guide at the same time. It explains why a bare screenshot is risky, why you should capture the original record wherever you can, and — if a screenshot really is all you have — how to certify it properly by hashing the image file and producing a Section 63 / 65B electronic-evidence certificate with e-Dex (formerly Hash Calculator).

Why a Bare Screenshot Is Risky

A screenshot is secondary evidence — an image of what was on a display, not the underlying record. It can be cropped to remove the context that follows or precedes it, edited in any photo app to change a number or a name, or produced wholesale by a fake-chat or fake-receipt generator. On its face it carries no provenance: nothing in the picture proves which device, account or app it came from, and nothing shows it has not been changed since it was taken. Because a screenshot is an electronic record, Indian courts generally expect it to be supported by a certificate rather than simply shown on a phone. So the question “is a screenshot admissible as evidence in India?” usually has the same answer: on its own it is weak and easily challenged. The good news is that you can almost always do better.

The Better Path — Capture the Original

Before you settle for a screenshot, ask whether you can capture the original record instead. In most situations you can, and it is far stronger. If the evidence is a chat, use the app's own Export feature to get the real transcript and media as files — the same approach in our guide to certifying a WhatsApp chat for court in India. If it is a web page or a social-media post, save the page itself — print to PDF or save as MHTML so the page content and its URL and capture date are preserved, not just a cropped image. If it is a payment or a transaction, obtain the actual bank or UPI statement from the bank or app rather than a screenshot of the confirmation screen. The original record carries its own structure, source and context, which is exactly what a screenshot throws away.

If a Screenshot Is Genuinely All You Have

Sometimes the original is gone — a message was deleted, an account was closed, a post was taken down — and a screenshot is the only surviving record. That is fine; you can still certify it, but you have to be honest about what it is and capture the surrounding facts. The goal is to turn an anonymous image into an exhibit tied to a real device, a real source and a real moment. That means recording which device took the screenshot, which app or source it shows, the date and time it was captured, and who captured it — and then hashing the image file so its exact bytes can be verified later. The steps below walk through this carefully.

Step 1 — Preserve the Source

Keep the device that took the screenshot, and the original record if it still exists, intact. Do not delete the underlying chat, post or message, and do not re-save, crop or “clean up” the screenshot — every such edit changes the file and weakens it. Note who holds the device and from when; that record — the chain of custody — is what lets you later explain how the screenshot reached the court untouched. If the original record is still live, prefer capturing it (the section above) and treat the screenshot as a backup.

Step 2 — Record the Particulars

Write down the facts while they are fresh. Record the device make and model that took the screenshot, the app or source shown (the chat app, website, bank app and so on), the account or URL involved where known, the date and time of capture, and who captured it. These particulars are what connect the image file to something real — exactly the questions a court will ask of any screenshot.

Step 3 — Hash the Image File

Now fingerprint the exact bytes of the screenshot. In e-Dex, add the original image file (the unedited .png or .jpg as the device saved it) and compute a cryptographic hash — SHA-256, and others such as SHA-512, MD5 or BLAKE3 if you wish. A hash is a fixed-length digital fingerprint: recompute it later and, if it matches, the file is bit-for-bit identical to what you certified; change a single pixel and the hash changes completely. This does not prove the picture is genuine, but it lets anyone — the court, the opposing party, your own expert — confirm the screenshot has not been altered since it was certified, without taking your word for it.

Step 4 — Generate the Certificate

With the file hashed, generate the certificate itself. e-Dex produces a Section 63 BSA / Section 65B evidence-integrity certificate that records the device, the source and the integrity hash, with an explicit MATCH verification against the screenshot. The output follows the familiar Part A / Part B Schedule form — Part A describing the electronic record and how it was produced, Part B listing the device and the hash value — so it reads the way a court expects. If you want to see the structure first, this Section 65B certificate format with an example is a useful reference.

Step 5 — Sign and Timestamp

Finally, make the certificate tamper-evident. e-Dex can apply a PAdES digital signature using a Digital Signature Certificate (DSC) on a USB token, binding the signer's identity to the document so any later edit is detectable. It can also attach an RFC-3161 trusted timestamp from a Time-Stamping Authority, providing independent proof that the certificate existed in that exact form at that moment. Both steps run from your own Windows machine; only the timestamp touches the internet, and everything else stays fully offline. Remember that e-Dex does not capture the screenshot for you — you take the screenshot (or export the original), and e-Dex then hashes and certifies the resulting file.

Common Pitfalls

A few mistakes account for most weak screenshot evidence. Cropping the image to show only the part you like removes the context a court needs and invites doubt. Editing — even harmless tidying — destroys trust in the picture entirely. Re-saving the screenshot (opening it in an editor and exporting again, or letting an app re-compress it) changes the file and breaks any earlier hash, so always certify the original as the device saved it. And no source context — no device, no app, no URL, no date, no capturer — leaves the court unable to connect the image to anything. Above all, relying on a screenshot when you could have captured the original is the biggest avoidable weakness; the steps here are designed to limit the damage when a screenshot is unavoidable.

A Note on Legal Advice

e-Dex helps you produce a well-structured, integrity-backed certificate; it is a tool, not legal advice and not a substitute for counsel. The Bharatiya Sakshya Adhiniyam 2023 replaced the Indian Evidence Act 1872 and came into force on 1 July 2024, and Section 63 BSA is the successor to Section 65B IEA — both require a certificate for electronic records tendered as secondary evidence. The Supreme Court in Arjun Panditrao Khotkar v. Kailash Kushanrao Gorantyal (2020) held that a Section 65B(4) certificate is a mandatory pre-requisite for admitting secondary electronic evidence, while recognising relief where a party genuinely cannot obtain it because the device is in someone else's possession. This is general information only, the law evolves and is now under the BSA, and who must depose to the certificate and how it is tendered depend on the facts of your matter — so read the current provision and the Schedule as they stand and take advice where the stakes warrant it. For a broader walkthrough, this guide to electronic-evidence certificates in India is a good starting point. e-Dex does not guarantee that any record will be admitted — that is for the court to decide.

Frequently Asked Questions

Is a screenshot admissible as evidence in India?
A screenshot is an electronic record, so under Section 63 of the Bharatiya Sakshya Adhiniyam 2023 (the successor to Section 65B of the Indian Evidence Act) it generally needs a certificate to be admitted as secondary evidence. It is not automatically admissible just because it is shown on a screen, and admissibility is ultimately decided by the court on the facts.

Why are screenshots considered weak evidence?
A screenshot is a picture of a screen, not the underlying record. It can be cropped, edited in any image tool or fabricated outright, and it carries no built-in proof of which device or app it came from. With no source context and no integrity proof, a bare screenshot is easy for the other side to challenge.

How do I make a screenshot court-admissible?
Wherever possible capture the original instead of a screenshot: export the chat, save the web page as a PDF with its URL, or obtain the actual statement. If a screenshot is genuinely all you have, record the device, the app or source, the date and time and who captured it, then hash the image file and produce a Section 63 / 65B certificate. The court still decides admissibility.

Do I need a Section 65B certificate for a screenshot?
A screenshot tendered as secondary electronic evidence generally needs a certificate under Section 63 of the Bharatiya Sakshya Adhiniyam 2023, which has replaced Section 65B of the Indian Evidence Act since 1 July 2024. The Supreme Court in Arjun Panditrao Khotkar (2020) treated such a certificate as a mandatory pre-requisite for secondary electronic evidence, so plan to provide one.

Can an edited screenshot be detected?
Not always from the picture alone, which is why screenshots are weak. Hashing the image file does not prove the picture is genuine, but it fingerprints the exact bytes so anyone can confirm the file has not changed since it was certified. Capturing the original record and preserving the source device give far stronger grounds to detect or rebut tampering.

Conclusion

A screenshot is the easiest evidence to produce and the easiest to attack. Whenever you can, capture the original — export the chat, save the page with its URL, get the real statement — and certify that instead. When a screenshot is genuinely all that survives, do not leave it bare: preserve the source, record the device, app, date and capturer, hash the image file and wrap it in a signed, timestamped Section 63 certificate so the court has something it can actually verify. Take the screenshot or export the original yourself, then let e-Dex — the Digital Evidence Integrity Suite hash the file, capture the details and generate a court-ready certificate on your own Windows machine, fully offline and free to try.