A software invention in India can qualify for copyright and patent protection at once, though the two work differently. Copyright protects the code as written expression and attaches automatically the moment it exists. A patent protects the claimed technical implementation, but only if it clears the “computer programme per se” exclusion in Section 3(k) of the Patents Act, 1970.
Deciding between a software patent or copyright registration, or pursuing both, depends on what the software actually does: whether it is expression that copyright already covers, or a technical effect that pushes it toward patent-eligible territory. India runs both regimes in parallel under the Patents Act, 1970 and the Copyright Act, 1957, with the Patent Office’s 2025 guidelines setting out how examiners apply the patent side of that line. Both statutes matter to the same product, and treating either one as the whole answer is where most generic coverage goes wrong.
Quick answer: Copyright protects your original software code automatically from the moment you write it. Patent eligibility is separate and claim-specific: a component clears Section 3(k)’s computer-programme-per-se exclusion only if it produces a technical effect beyond ordinary program execution, though clearing that exclusion is not by itself a guarantee of grant, and a claim that is, in substance, a business method is excluded regardless of technical effect. See the three-scenario test below to place your own product.
What counts as a “software invention” under Indian law
Indian law does not define “software” in any statute. Both the Patents Act, 1970 and the Copyright Act, 1957 work with related but separate terms instead, “computer programme” for copyright and the excluded category of “computer programme per se” for patents, and examiners fall back on the ordinary dictionary meaning when the term itself needs interpreting.
For interpretive purposes, the Patent Office’s Guidelines for Examination of Computer Related Inventions (CRI Guidelines) 2025 quote the Oxford Advanced Learner’s Dictionary definition, “the programs, etc. used to operate a computer,” and the Cambridge Dictionary’s “the instructions that control what a computer does; computer programs.” Neither definition distinguishes source code from object code, or a standalone program from a component embedded in a larger system. That gap is why the same software can be a literary work for copyright purposes and a computer-related invention for patent purposes at once, evaluated under two different tests. The Patent Office’s own practice manual, an administrative guide rather than a statute, reflects the same split for exclusion purposes: literary and artistic works, including computer programmes, are treated as falling within the Copyright Act’s domain rather than the patent system for that purpose, which is why the technical-effect analysis below is reserved for the patent side of the line; the two regimes can still apply to the same product on different aspects, as the rest of this article shows.
How copyright protects software in India
Copyright protection for software in India attaches automatically to original code the moment it is written, covering the computer programme as a literary work, with no registration required. The Copyright Act, 1957 defines “computer programme” at Section 2(ffc) and brings it within “literary work” at Section 2(o).
That places source code alongside any other literary work for the reproduction, adaptation and communication rights the Act gives, plus one right specific to software: Section 14(b) also gives the copyright owner the right to sell or commercially rent out copies of the programme, a right a novel’s copyright does not carry in the same form.
That definition covers “a set of instructions expressed in words, codes, schemes or in any other form, including a machine readable medium, capable of causing a computer to perform a particular task or achieve a particular result.” Because copyright subsists in original literary works under Section 13 without any registration precondition, protection exists the moment qualifying code is fixed in some tangible form, such as being saved to a file.
Subsistence itself turns on the author’s Indian citizenship or domicile, or on the software being first published in India (Section 13(2)), with separate rules extending protection to foreign works. Registration with the Copyright Office is available and useful as evidence, covered further below, but it is not what creates the right.
For software published during the programmer’s lifetime, copyright runs for the author’s lifetime plus 60 years, counted from the start of the calendar year after the author dies (Section 22 of the Copyright Act, 1957), a far longer window than a patent ever offers; unpublished code, or code first published after the author’s death, falls under the Act’s separate rules for those cases. What copyright protects is narrower than its term suggests, though: the expression fixed in the code, not the underlying method, algorithm, or functionality that code carries out.
How patents protect software in India
A patent protects the claimed technical implementation a piece of software embodies, not the code itself and not simply the same real-world result reached another way, and only if the invention as a whole clears Section 3(k) of the Patents Act, 1970, which excludes “a mathematical or business method or a computer programme per se or algorithms” from patentability.
Each of those exclusions works differently. The “per se” qualifier attaches to “computer programme” specifically: a claim is not excluded merely for being implemented in software, provided it clears the technical effect test below. Algorithm claims are excluded or not under their own separate test, turning on whether the claimed steps are enabled with the technical specifics needed to implement them and solve a real-world problem, rather than left as an abstract sequence; a claim that is, in substance, a business method faces a further, absolute bar in India regardless of any technical effect it shows, a distinction the case law below makes explicit. The Joint Parliamentary Committee’s 2001 report on the amending bill explained why “per se” was added to the computer-programme limb: the computer programme “as such” is not meant to be patented, but a programme with “certain other things, ancillary thereto or developed thereon” is not rejected for that reason alone, per the CRI Guidelines 2025. That line is drawn using the technical effect test covered next, not the claim language alone.
A patent, once granted, lasts 20 years from the date of filing (Section 53 of the Patents Act, 1970), regardless of when the grant issues, and stays in force only if renewal fees are paid on schedule. A patent that lapses for non-payment is not automatically gone for good: the patentee may apply to restore it within 18 months, though restoration is not automatic either. The Controller must be satisfied the failure was unintentional and that there was no undue delay, the application is then published, and anyone interested may oppose it on those two specific grounds (Sections 60 and 61 of the Patents Act, 1970). That is a shorter window than copyright’s term, but within the scope the granted claims actually cover, a patent also stops a competitor from using the same claimed implementation; copyright only stops them from copying your code. Clearing the examiner’s technical effect analysis comes first, the subject of the next section; Intepat’s software and AI patents team can take it from there once you are ready to file.
The “technical effect” test: when software crosses into patentable territory
Indian courts assess computer-related inventions by asking whether the claimed solution produces a “technical effect” or “technical contribution” beyond the ordinary running of a program on standard hardware. The cases below, decided by the Delhi and Madras High Courts since 2019, turn on different limbs of Section 3(k) (per se, algorithm, or business method) and use related rather than identical formulations.
The test traces back to Ferid Allani v. Union of India (Delhi High Court, 2019), which held that a claim showing a technical effect or technical contribution should not be refused under Section 3(k) merely because it runs on a computer. That rescue route runs through the computer-programme-per-se limb specifically; a business-method claim faces a further, absolute bar regardless of any technical effect it shows, which Indian courts treat as excluded outright, unlike the position in the UK or under the European Patent Convention. Later decisions applied and sharpened the technical-effect approach across a range of software claims:
| Case | Court and date | What it decided |
| Ferid Allani v. Union of India | Delhi HC, 12 Dec 2019 | Technical effect or technical contribution is the test; a computer implementation alone is not disqualifying |
| OpenTV Inc v The Controller of Patents and Designs | Delhi HC, 11 May 2023 | Unlike the computer-programme limb, the business-method exclusion is absolute; the only question is whether the claim addresses a business or administrative problem |
| Raytheon Company v. Controller General of Patents and Designs | Delhi HC, 15 Sept 2023 | No requirement for novel hardware; look at the technical contribution instead |
| Microsoft Technology Licensing LLC v. Assistant Controller of Patents and Designs | Delhi HC, 15 May 2023 | A technical solution going beyond the user-interface level, into network-level or system-level operation, can be patentable |
| Microsoft Technology Licensing LLC v. The Assistant Controller of Patents and Designs | Delhi HC, 16 April 2024 | The applicant must show a specific, credible technical effect beyond general-purpose computing |
| Microsoft Technology Licensing LLC v. Assistant Controller of Patents and Designs | Madras HC, 3 July 2024 | Improving how the system itself functions, or solving a technical problem technically, overcomes Section 3(k) |
| Ab Initio Technology LLC v. Assistant Controller of Patents and Designs | Delhi HC, 30 July 2024 | The technical effect must go beyond the user interface |
| BlackBerry Limited v. Assistant Controller of Patents and Designs (C.A.(COMM.IPD-PAT) 229/2022) | Delhi HC, 30 Aug 2024 | A bare set of instructions that only determines a data flow is not patentable; software that implements an algorithm and produces a technical effect can be, and novel hardware is not required |
Worth noting before the examples below: each of these cases originated in a Patent Office refusal under Section 3(k). Most reached the High Court on a direct statutory appeal from that refusal; Ferid Allani is the exception, reaching the High Court by writ petition after the since-abolished Intellectual Property Appellate Board had already dismissed a statutory appeal from the same refusal, and the High Court there remanded the matter back to the Patent Office rather than deciding patentability itself. Nor did every case end with the refusal overturned: in Blackberry, the Delhi High Court restated the legal test but still dismissed the appeal and upheld the refusal on the facts. None of this supports estimating how often a Section 3(k) claim in general succeeds on appeal, since these cases are, by definition, drawn only from claims that were refused first.
The CRI Guidelines 2025 illustrate, with two non-exhaustive lists, which side of the computer-programme-per-se line an aspect of an invention tends to fall on. Clearing this exclusion is necessary but not sufficient for a grant: the invention still has to satisfy novelty, inventive step, and the Act’s other requirements, assessed separately.
| May avoid the computer-programme-per-se exclusion | Tends to fall under the exclusion |
| An algorithm that measurably speeds up data processing, or a more efficient caching or storage architecture | A claim to code, a storage medium, or a database considered in isolation |
| Better search or indexing, stronger compression, or improved authentication security | A search or recommendation feature built on standard keyword matching or user profiling, without more |
| Real-time control of physical devices, such as robotics, IoT sensors, or autonomous systems | A rule-based tool that mimics human judgment without a specific technical implementation |
| Measurably more efficient training of a machine-learning model, or a novel neural network architecture | Automating a manual task such as bookkeeping or scheduling without technical gain |
Every category above is illustrative, not exhaustive, and describes only this one exclusion; a claim is judged on what it actually does, not on which list it superficially resembles, and still needs to clear the Act’s other requirements to be granted.
Software patent or copyright: which should you choose?
Original software code attracts copyright automatically, at no cost and with no filing. Patent eligibility is a separate, claim-specific assessment, turning on whether a specific technical component produces a technical effect beyond the ordinary running of a program, not on how much of the product the code represents or how the rest of it is built.
Three scenarios cover most products, judged claim by claim rather than product by product, since one application can combine a copyright-only feature with a separately patentable technical component:
- Pure code with no measurable technical effect, or a business method dressed in software: a typical business-logic app, a straightforward interface, a bookkeeping tool, or a pricing or scheduling engine built on standard rules. Copyright is the only realistic IP route for that component, and it already applies automatically; confidentiality or contract terms can supplement it where relevant, a separate question from patent eligibility.
- Code that produces a measurable technical effect on hardware or system performance: faster processing, better compression, a genuinely novel security mechanism, or improved control of a physical device. That technical effect can clear the Section 3(k) exclusion, making a patent application worth exploring for that component; whether one is actually granted still depends on novelty, inventive step, and the Act’s other requirements, assessed separately. Copyright still attaches to the code regardless.
- Genuinely unsure which category the software falls into. A provisional patent application, a short written description that secures a priority date without needing finished claims, can preserve that date for claims later shown to be fairly based on what it disclosed (Section 11, Patents Act, 1970), while the technical contribution is worked out; a complete specification must follow within 12 months (Section 9, Patents Act, 1970), or the application is treated as abandoned. Copyright continues to cover the code in the meantime at no extra cost.
Startups weighing that cost are not without help: separate filing fee concessions apply for eligible startups, covered in Intepat’s guide to patent benefits for MSMEs.
One rough, non-legal way to sense-check which bucket a feature falls into: could a competitor reach the same result a different way about as easily? If yes, that is a signal the value sits in the expression, where copyright already does the work. If no, because the software solves a technical problem in a way that is not obvious to recreate, that is a reason to get a patent attorney’s opinion, since the real answer turns on novelty, inventive step, and Section 3(k), not on this heuristic alone. Either way, get that opinion before the first public disclosure where possible: publicly showing, selling, or describing the invention beforehand can destroy the novelty a patent depends on, subject only to narrow statutory exceptions such as a notified exhibition, a paper read before a learned society and filed within 12 months, or use for reasonable trial (Sections 29 to 34, Patents Act, 1970); none of those exceptions will cover most ordinary product launches, so filing first remains the safe default.
Registering software copyright: what Rule 70 actually requires
Copyright in software exists without registration, but registering it with the Copyright Office creates useful evidence of authorship and ownership. Rule 70 of the Copyright Rules, 2013 sets out what an application for a computer programme must include, and the source-code requirement is narrower than many applicants expect.
Every application for registration of a computer programme must be accompanied by “at least first 10 and last 10 pages of source code, or the entire source code if less than 20 pages, with no blocked out or redacted portions” (Rule 70(5) of the Copyright Rules, 2013); the requirement covers source code only, with partial submission available once the source code passes the 20-page mark, and the complete source code required below that threshold.
Rule 70(1) sets the application form itself, Form XIV for a fresh registration; the fee, signatures, and accompanying documents are set out in the sub-rules that follow.
One of those sub-rules catches many applicant companies off guard: where the applicant is the copyright owner rather than the individual author, such as a company registering code an employee or contractor wrote, the application must include an original no-objection certificate signed by that author (Rule 70(3)), worth tracking down early, especially for code written by former employees or contractors. The Copyright Office does not examine software for originality the way a patent examiner tests for inventive step, but registration is more than an informal timestamp: once entered, the particulars in the Register of Copyrights stand as prima facie evidence in legal proceedings of what they record (Section 48, Copyright Act, 1957), which is why registration is worth having even though it does not create the underlying right. For a step-by-step walkthrough, see Intepat’s guide to copyright registration procedure in India, or the software copyright registration service if you are ready to file.
How the US and EU treat software patents
Major patent offices outside India, including the US Patent and Trademark Office (USPTO) and the European Patent Office (EPO), apply their own tests for software patent eligibility, each shaped by its own statute and case law. Those tests are not interchangeable with Section 3(k), and a side-by-side comparison is outside this article’s scope.
Intepat’s coverage of responding to USPTO office actions and of comparative European and Indian patent practice goes into the detail a real filing decision needs.
Frequently asked questions
Yes. Copyright and patent protect different things, so both can apply to one product. Copyright covers the code you wrote, automatically, from the moment it exists. A patent, if the invention clears Section 3(k) and the Act’s other requirements, covers the claimed implementation, which can stop a competitor using that implementation in different code, within the scope the granted claims cover.
Just the code you wrote, not the underlying idea. Copyright does not extend to the method or functionality your software carries out, only to the particular way you expressed it. A competitor who independently writes different code to do the same thing has not infringed your copyright. Intepat’s piece on the idea-expression dichotomy covers this boundary in depth.
For software published during the author’s lifetime, copyright lasts for the author’s lifetime plus 60 years, counted from the start of the calendar year after the author dies (Section 22 of the Copyright Act, 1957). Unpublished software, or software first published after the author’s death, follows the Act’s separate rules for those cases instead.
Usually not, for that version. Patent law requires the invention to be new when filed; publicly showing, selling, or describing it beforehand can destroy that novelty, subject to narrow exceptions such as a notified exhibition or a learned-society paper filed within 12 months (Sections 29-34). Talk to a patent attorney immediately if disclosure has happened. Copyright is unaffected, since it never depended on secrecy.
For an employee under a contract of service, the employer owns the copyright by default, absent an agreement otherwise (Section 17); the Act does not require that agreement in writing, though writing helps. For a contractor or freelancer, ownership stays with the contractor unless a signed, written assignment transfers it (Section 19), which can be signed for a future work before it exists (Section 18), so signing early helps.
Twenty years from the filing date (Section 53, Patents Act, 1970), or the international filing date for a PCT application designating India, regardless of examination time. The patent stays in force only while renewal fees are paid on schedule; a missed fee can be fixed by applying to restore the patent within 18 months, subject to the Controller’s satisfaction and possible opposition (Sections 60 and 61).
No. Copyright in a computer programme arises automatically once the code exists in fixed form; India does not condition copyright on registration. Registering with the Copyright Office is optional, useful as dated evidence of authorship if a dispute arises later. Rule 70 of the Copyright Rules, 2013 sets out what that application must contain, including source-code pages.
It means the bare program on its own, with nothing else added. Section 3(k) excludes a computer programme per se from patentability, but not an invention merely implemented through software. Where the software produces a technical effect, such as making a system run faster or more securely, courts have held the per se exclusion does not apply.
This article explains the position in India as at August 2026 and is for general information only. It is not legal advice. Laws, fees, and procedures change; verify the current position before you act. For advice on your specific matter, consult a qualified IP professional.