Admissibility of Digital Evidence in India: 2026 Guide

Digital evidence now appears in almost every serious dispute: emails, WhatsApp chats, call records, screenshots, server logs, CCTV clips, cloud documents, payment trails, location data and social media posts. The practical question is rarely whether a record is digital. The question is whether the party relying on it can prove it in a manner the court can safely act upon.

In 2026, admissibility must be understood against two connected regimes. For proceedings governed by the new criminal law framework, the Bharatiya Sakshya Adhiniyam, 2023 recognises electronic and digital records as documents and provides a specific route for proving their contents. For older proceedings and many civil records still argued through familiar terminology, the principles developed under Sections 65A and 65B of the Indian Evidence Act, 1872 remain highly relevant. The language has evolved, but the core discipline remains the same: identify the record, explain the device or system that produced it, show regular use, and preserve integrity.

Relevant Indian Legal Framework

The Bharatiya Sakshya Adhiniyam treats electronic and digital records as documentary evidence. Section 61 gives electronic records legal effect subject to the special proof provision. Section 62 states that contents of electronic records may be proved in accordance with Section 63. Section 63 is the modern counterpart to the certificate-based rule familiar from Section 65B. It covers information printed, stored, recorded or copied in electronic form and requires conditions relating to regular use of the computer or communication device, ordinary course input, proper operation and accurate reproduction.

For litigation teams, the important point is that admissibility is not a clerical afterthought. A screenshot forwarded by a client, a PDF exported from a system, a CD prepared by an investigator or a downloaded chat file may all be secondary electronic outputs. Unless the original device is produced and inspected in a legally meaningful way, the party should be ready with the required certificate and supporting witness.

Recent Case Law Principles

In Anvar P.V. v. P.K. Basheer, the Supreme Court held that electronic records offered as secondary evidence must satisfy the statutory certificate requirement. Shafhi Mohammad v. State of Himachal Pradesh temporarily softened that approach for parties who did not control the device. The position was clarified in Arjun Panditrao Khotkar v. Kailash Kushanrao Gorantyal, where the Supreme Court reaffirmed that the certificate requirement is mandatory for secondary electronic evidence, while also recognising that a party unable to obtain a certificate may seek assistance from the court to summon it from the person in control.

Other authorities remain useful. Sonu alias Amar v. State of Haryana indicates that objections to mode of proof should be taken at the appropriate stage. Tomaso Bruno v. State of Uttar Pradesh demonstrates how missing electronic evidence can affect appreciation of facts. P. Gopalkrishnan v. State of Kerala highlights the evidentiary and fair-trial importance of cloned copies and access to electronic material. Together, these cases show that courts look beyond labels. They ask whether the record is relevant, authentic, properly produced and fairly available for challenge.

Practical Preparation

A production-ready evidence plan should start before litigation is filed. Identify the source device or platform, the custodian, the period covered, the manner of extraction, the hash value or other integrity marker, and the reason the record is relevant. Preserve the original device where feasible. If the evidence sits with a bank, telecom provider, cloud service, employer or platform administrator, request certified records early and keep a clean trail of correspondence.

Parties should avoid altering metadata by forwarding files casually, renaming exports repeatedly or opening files in applications that modify last-accessed information. Where digital evidence is central, a forensic image or supervised extraction may be more persuasive than ordinary screenshots. The certificate should not be generic. It should identify the record, describe the manner of production, state device particulars and address the statutory conditions in clear language.

The most common error is treating admissibility and evidentiary weight as the same issue. A document may be admitted and still carry little weight if it appears incomplete, manipulated or unexplained. Conversely, a highly relevant record may never be considered if its mode of proof is defective and the objection is timely. Another mistake is waiting until trial to locate the certificate signatory. By then, the employee may have left, the device may be replaced and the platform record may have expired.

Digital evidence works best when legal and technical teams collaborate. Lawyers frame relevance and pleadings. Forensic specialists preserve integrity. Custodians explain systems. Together, they create a record the court can understand and the opposing party can test. That discipline is now a core part of serious litigation strategy in India.

Litigation Checklist for 2026

At the filing stage, counsel should prepare an evidence map. The map should identify each electronic record, the fact it proves, the source system, the custodian, the available original, the proposed certificate signer and the likely objection from the other side. This exercise is useful because digital evidence often multiplies quickly. One commercial dispute may involve contract emails, WhatsApp instructions, payment screenshots, login records and CCTV footage. If each item is not linked to a pleaded fact, the record can become bulky without becoming persuasive.

At the preservation stage, the client should be told to suspend routine deletion. Auto-delete settings in messaging apps, email retention policies, CCTV overwrite cycles and cloud sync rules can destroy evidence without any deliberate misconduct. If a device is likely to be relevant, preserve it in its existing state. If business continuity requires continued use, take a forensic image or controlled export first. Keep a simple custody note recording who collected the device or data, when it was collected, how it was stored and whether hash values were generated.

At the production stage, avoid mixing evidentiary forms. A printed screenshot, a PDF export and a native file may all depict the same conversation, but they do not carry the same technical value. Native exports and source metadata can help answer authenticity challenges. Screenshots help the court see what the user saw. Certificates help satisfy the statutory route. A strong filing explains why each form is included and avoids presenting duplicated material as separate proof.

At trial or final hearing, be ready to prove context. Digital evidence rarely speaks entirely for itself. The court may need to know who used the device, whether the account was shared, why the timestamp matters, whether the record is complete, and whether the opposing party had a fair chance to inspect or challenge it. A witness who understands the record is often as important as the certificate. In sensitive matters, the court may also need assistance on redactions, privacy, privilege and confidential business information.

The best practice is therefore not merely to collect digital evidence, but to manage it as a litigation asset. A record that is relevant, preserved, certified, contextual and proportionate is more likely to survive objection and assist the court on merits.

For 2026 filings, teams should also remember transition issues. Older disputes may still refer to the Indian Evidence Act and Section 65B, while newer proceedings may cite the Bharatiya Sakshya Adhiniyam and Section 63. The safest drafting practice is to identify the applicable procedural context and, where appropriate, explain the continuity of principle between the two regimes. This avoids needless argument about labels and keeps the court focused on reliability, authenticity and fairness.