Software Copyright Registration in Nepal: A Practical Guide for Developers
Software copyright registration in Nepal: what the Copyright Registrar's Office process involves for code, what deposits to prepare, and why assignments come first.
Nepal's copyright law protects software as a literary work automatically from the moment the code is written — but try proving that in a dispute, a funding diligence or a platform takedown, and the automatic right meets the paperwork question.
Software copyright registration in Nepal is the voluntary answer: a dated, government-issued record of ownership at the Copyright Registrar's Office. This guide walks the process as developers actually experience it.
In short
Software copyright registration in Nepal is voluntary but valuable: protection exists automatically under the Copyright Act, 2059 (2002), and registration at the Copyright Registrar's Office — through its online portal or in person — adds a presumptive ownership record that investors, acquirers and platforms accept without argument. The process: prepare deposits of the code (typically key excerpts with version documentation), assemble ownership papers (assignments from every employee, freelancer and contractor), file with the prescribed fee, and take the certificate. Fix the chain of title first — registration records ownership as filed and cannot cure a missing assignment.
What registration proves — and what the law already gives
The Act protects a program's code from creation, without formalities — the moment the code is written, the rights exist. Registration adds nothing to the right itself. What it adds is proof: a public, government-issued, dated certificate stating the work, the author and (where assigned) the owner.
That certificate does heavy lifting in the situations software companies actually face: investor and acquirer diligence (unassigned or unproven IP is the most common finding in Nepalese startup reviews), platform takedowns (documented ownership moves faster), licensing negotiations (licensees demand clean chains), and disputes with departed developers or contractors.
Before filing: fix the chain of title
Registration records the ownership as filed — it cannot cure it. The defect that matters is authorship without assignment: employees who never signed IP clauses, freelancers who delivered code without written transfer, agencies whose contracts are silent. Registering the codebase in the company's name while a contractor's assignment is missing creates a certificate that fails precisely when challenged.
The pre-filing audit is short: list the codebase's contributors, identify every creator without a signed assignment, execute retroactive assignments now — then register. The assignment work costs less than the registration and matters more.
Software copyright registration in Nepal: the filing, step by step
The Registrar's process is straightforward, and the online portal has removed the queue:
Prepare the application details
Applicant (author and/or owner — they differ when rights are assigned), the software's title, type, and creation or first-release dates. Keep the submission receipt: it dates the application.
Prepare the deposits
The work itself, as the category requires: for software, source code deposits — typically representative excerpts plus documentation of the version registered. Decide the excerpt scope deliberately; the deposit is what the certificate describes.
Attach the ownership papers
Where the applicant is not the author: the written assignments — the underlying chain of title. Employment IP clauses and contractor agreements belong in this folder.
File and pay the prescribed fee
Submission through the portal or at the Registrar's Office with the prescribed per-work fee. Each work registers separately — a codebase and a website file as two registrations.
Examination and certificate
The Registrar examines formal compliance — category, deposit, documents. This is a recordal with scrutiny, not an adjudication of originality. The certificate issues with the registration details; file it with the assignments in the chain-of-title folder.
What to register in a codebase of many works
Software products are bundles of works — the core codebase, the mobile clients, the design system, the website — and per-work registration makes selectivity sensible. The works that justify their fee:
| Work | Register? | Why |
|---|---|---|
| Core platform codebase | Yes | Diligence and enforcement evidence for the company's main asset |
| Flagship app client | Yes | Platform takedowns and clone disputes run on it |
| Website content and brand assets | Selective | Register what is licensed or copied; the rest stays protected anyway |
| Every internal tool and script | No | Protection exists automatically; registration adds cost without a dispute target |
Copyright vs. the other software protections
Registration is one layer of the stack. Copyright protects the code's expression, not its function — a competitor may independently write different code for the same behaviour. The patent route for software is narrow in Nepal and rarely the practical tool. The brand layer is trademark: the app name and icon as device marks at the DOI (Class 9 and Class 42 filings, NPR 1,000 + NPR 5,000 per class). The secrecy layer is contractual: NDAs, employment terms and access controls around source code.
For most Nepalese software businesses the correct sequence is: assignments, copyright registration for the core code, trademark filings for the name and logo, and trade-secret discipline for everything that should never leave the building.
A note on what the certificate does not cover
Copyright never protects ideas, methods, algorithms as such, or titles and names — the certificate inherits those limits. And it does not substitute for contracts: an assignment recorded is worth more than a registration filed. The certificate is the capstone on a clean chain, not a repair for a broken one — which is why the order of operations in this guide is assignments first, registration second, enforcement third.
Want this handled for your brand?
IP Watch monitors new trademark publications in Nepal and alerts you to potentially conflicting marks — with the context needed to review them.
This article is general information, not legal advice.