Indian copyright law treats computer programmes as literary works under Section 2(o) of the Copyright Act, 1957. They sit alongside books, articles, lyrics and academic papers in the literary-work category, and attract the same Section 13(1)(a) protection. The doctrinal placement seems unusual to programmers but is the global norm — code is text that expresses creativity, and copyright protects the expression, not the underlying ideas or algorithms.
This guide covers how Indian copyright applies to software, what originality means in code, who owns code in employment and freelance settings, what reverse engineering Section 52 permits, and how open-source licensing intersects with proprietary code protection.
The statutory basis
Section 2(o) of the Copyright Act defines a literary work to include computer programmes, tables and compilations including computer databases. Section 13(1)(a) makes literary works the subject of copyright. Section 14(b) lists the exclusive rights of the owner — reproduction, distribution, adaptation, public performance, communication to the public, and the right to make a translation or any other adaptation.
The protection covers source code (the human-readable form) and object code (the compiled binary) equally. Both are 'computer programmes' within the statutory definition. Indian courts have confirmed this across multiple software-copyright matters, including infringement actions against unauthorised distribution of pirated commercial software.
Copyright protects the code. The algorithm — and the function the code performs — needs a different filing.
What 'originality' requires
Indian courts apply a 'sweat of the brow + modicum of creativity' standard to originality, drawing on Eastern Book Company v. D.B. Modak (2008, Supreme Court) and the line of cases applying that standard. For software, the threshold is generally satisfied where the code is:
- Independently created by the author (not copied from another source)
- Involves some intellectual effort and creative choice in expression — variable naming, logical structure, comments, code organisation
- Goes beyond purely functional or stereotypical expressions
Most non-trivial software code easily meets this threshold. Routine code — automatically generated, transparently functional, or borrowed from common libraries — may not. Open-source code modified by a developer carries the original author's copyright in the unchanged portions and the modifier's copyright in the new portions.
Idea-expression dichotomy
Copyright protects the expression, not the idea, the function, or the algorithm. A copyright-protected piece of software does not give the owner a monopoly over the function that software performs. Two developers independently writing implementations of the same algorithm — say, two implementations of QuickSort — produce two separately copyrighted works that may both be entirely lawful.
This is the key distinction from patent law. A patent on a software-implemented invention (subject to Section 3(k)) covers the method or system, blocking independent implementations. Copyright on a piece of code covers only that specific expression; an independent implementation does not infringe.
Ownership — Section 17 in software context
Section 17 of the Copyright Act determines first ownership:
- Section 17(a) — author by default. Independent code, founder code before incorporation, weekend personal projects
- Section 17(c) — employer owns code written by employees in the course of employment. The standard rule for in-house code
- Section 17(c) does NOT apply to freelancers — freelance code defaults to the author. The hiring company needs a written Section 18-19 assignment to acquire ownership
Indian software companies and SaaS startups must structure freelancer and contractor agreements with explicit IP assignment clauses. The omission is one of the most common findings in IP due diligence reviews at funding rounds.
Reverse engineering under Section 52
Section 52(1)(aa) through (ad) of the Copyright Act provides specific exceptions for computer programmes:
- 52(1)(aa) — making back-up copies for archival purposes
- 52(1)(ab) — making copies necessary to obtain information essential for operating interoperability of an independently created computer programme with other programmes, by a lawful possessor, provided the information is not otherwise readily available and the copies are not used for other purposes
- 52(1)(ac) — observing, studying or testing the functioning of the programme to determine the ideas and principles underlying any elements, while performing any of the acts a lawful user is permitted
- 52(1)(ad) — making copies during the lawful use of the programme
The interoperability exception (52(1)(ab)) is the most strategically important. Indian developers building plug-ins, integrations or competitive products that need to communicate with proprietary software can rely on (ab) to perform necessary reverse engineering — within the narrow scope the section permits.
Open-source licensing
Software using open-source components must comply with the relevant licence terms. Major Indian software products integrate dozens of open-source libraries; compliance is operational. The major licence categories and their core obligations:
- MIT, BSD, Apache 2.0 (permissive) — attribution required; no copyleft obligation. Can be combined with proprietary code freely
- LGPL (weak copyleft) — modifications to the LGPL-licensed library must be released under LGPL; proprietary applications can dynamically link to it without proprietary code becoming GPL
- GPL v2, GPL v3 (strong copyleft) — distribution of derivative works requires those works to be released under GPL. Mixing GPL with proprietary licensing creates compliance exposure
- AGPL (network copyleft) — extends GPL to network-delivered software (SaaS). Strict compliance challenges for proprietary SaaS products
Open-source compliance is the operational standard. Pre-launch open-source audits — identifying every component, its licence, and the obligations triggered — are common practice for any Indian software product going to commercial distribution.
Building software in India? Founder IP assignment, freelancer Section 18-19 assignments, open-source compliance — the copyright stack is real. Send us the architecture and the team structure, we'll spot the gaps.
WhatsApp our team →Registration — voluntary but valuable
Copyright in India arises automatically on creation; registration with the Copyright Office is not required for protection. But registration provides an evidentiary register — a certificate of registration is prima facie evidence of ownership and authorship in Indian courts. For valuable proprietary software, periodic registration of major versions is the standard practice.
The takeaway
Indian copyright protects software code as a literary work. The protection is automatic on creation and covers source and object code. Ownership defaults to the author unless Section 17 or a written assignment changes that. Open-source components carry their own licence obligations that compose with proprietary protection. The interoperability and back-up exceptions under Section 52 give Indian software developers limited but real reverse-engineering rights. For Indian SaaS companies, product startups and contract development organisations, the copyright file is the foundation of the IP portfolio — alongside trade marks, patents and contractual IP allocations.
Your brand is only yours when you file it.
10,000+ Indian brands filed with IPForte. 48-hour turnaround. 130+ countries via Madrid Protocol. First call is free, no commitment.