Software copyright registration in Nepal is voluntary. A computer program can be protected from creation under the Copyright Act 2059 (2002), while registration gives its owner a dated official record. The filing goes to the Nepal Copyright Registrar's Office—not the Department of Industry.
The hard part is rarely the form. It is identifying the exact version, the people who wrote it, the components they did not write, and the documents that place the economic rights with the applicant.
Key takeaways
- Sec. 5 says registration is not required to acquire copyright.
- The Act expressly includes computer programs among protected works.
- Copyright protects original expression in code, not the underlying idea, function or method of operation.
- A company should document its chain of ownership before it applies.
- Register a clearly identified release or build, not a changing repository.
- Remove credentials, personal data and unrelated confidential material from any filing copy.
- Software names and logos are trademark questions; a qualifying technical invention may raise a separate patent question.
Is software protected by copyright in Nepal?
Yes. The definition of “work” in the Copyright Act 2059 includes computer programs. Sec. 5 then states that registration is not required to acquire the right. Original code therefore does not wait for a certificate before copyright exists.
Registration is an evidence step. It can connect a named claimant, a described program and a filing date in one official record. It does not create originality, validate the program's security or decide a disputed development contract.
The broader rules are explained in our guide to copyright registration in Nepal. Software teams should also keep repositories, signed releases, tickets, design records and contributor agreements because no certificate captures the full development history.
What part of a program does copyright protect?
Copyright protects original expression fixed in the program: the developer's selection and arrangement of code, and other original material such as documentation, icons, interface artwork and written screen content. It can apply to source code and to a compiled program as expressions of the same development work.
Protection is not ownership of every short command, programming language or standard technique appearing in the repository. The question is whether another person copied protectable expression, not simply whether two programs perform a similar task.
A filing should describe the protected work precisely. “Accounting platform, version 2.4, server and web-client code fixed on [date]” is more useful than “all software owned by the company.”
What remains outside software copyright?
Sec. 4 excludes a thought, concept, principle and method of operation, among other subject matter. A business idea, workflow, mathematical principle or desired output does not become private property merely because one developer implemented it first.
That distinction matters when competitors build independently. Similar functions are not automatically infringement. Evidence of access, identical unusual choices, copied comments, matching defects or substantial replicated structure may tell a different story, but the legal assessment is fact-specific.
Who owns code written by employees or contractors?
Start with Sec. 6(1): the author is the first owner, and neither employment nor payment transfers ownership by itself, so the company needs a signed written assignment (Sec. 24); moral rights stay with the author. Then read the actual employment, development or commission agreement. Labels such as “employee,” “vendor” and “co-founder” do not answer every ownership question by themselves.
Section 24 permits the owner to transfer economic rights by written agreement. A company relying on a transfer should have a signed document identifying the relevant code and the rights transferred. Payment records and invoices support the history but should not substitute for clear ownership language.
List every person whose original contribution remains in the build, including founders, former staff and outside agencies. If a developer brought pre-existing libraries into the project, identify them separately rather than claiming the company authored everything.
Why register software if protection is automatic?
A registration record can help during investment due diligence, licensing, acquisition talks or a copying dispute. It lets the company point to an identified version and an asserted owner on a known filing record.
Its limits matter equally. Registration does not prove that every contributor assigned rights, that third-party code was used within its licence, or that later releases are identical to the filed copy. It is one item in an evidence file, not a substitute for that file.
Which version of the software should you register?
Choose a stable, commercially meaningful release. Create an immutable archive, record its release or commit identifier, and make the filing description match that archive. A certificate for an unnamed “current version” becomes difficult to compare with code years later.
Major rewrites may justify a later filing because they contain substantial new expression. Routine bug fixes do not need automatic refiling. Decide by looking at the value of the new material and the evidence risk.
How much source code should you submit?
Confirm the current specimen and format requirement directly with the Registrar's Office before preparing the filing. Do not assume an online checklist from another country applies in Nepal, and do not send an entire production environment merely because it is convenient.
Create a clean filing copy that corresponds to the described build. Exclude passwords, API keys, signing certificates, customer records, access tokens and personal data. Keep an internal hash and complete archive so the submitted material can later be tied to the release.
What documents should a software applicant prepare?
| Record | What it should establish | Check before filing |
|---|---|---|
| Version record | The exact program being identified | Release, commit and date agree |
| Contributor list | Who created each original part | Founders and former developers included |
| Ownership documents | Why the applicant owns the economic rights | Written terms cover the relevant work |
| Component list | What belongs to third parties | Licences and notices are retained |
| Filing copy | The work presented to the office | No credentials or personal data remain |
- The applicant's legal name, address and authority documents.
- The program title, version, category, creation date and concise description.
- Names and roles of the developers and other authors.
- A copy or specimen in the format currently accepted by the office.
- Employment terms, development agreements and written assignments supporting ownership.
- A component list separating original, licensed and open-source material.
- Publication or release details, where the program has been made available.
- Agent authority, if a representative files.
The checklist changes with the applicant and work. Confirm the current form and supporting documents rather than treating this list as an official substitute.
How does the registration process work?
- Freeze the version. Record the release, commit and date.
- Map contributors. Identify authors and the material each supplied.
- Audit ownership. Locate employment terms, assignments and third-party licences.
- Prepare a safe copy. Follow the office's current format without exposing secrets or personal data.
- File with the Copyright Registrar's Office. Keep the acknowledgement and an exact copy of the submission.
- Answer any query. Make corrections transparently and retain the final certificate with the evidence bundle.
For the general administrative route, see our copyright registration process guide. The office is separate from our trademark registration, patent registration and industrial design services.
Does the Registrar examine novelty or publish an opposition notice?
No. Copyright registration is not a patent examination and does not establish that the software is technically new. It also does not follow the trademark bulletin and opposition process.
There is no public per-work copyright search comparable to IP Sewa's Nepal trademark database. That means a blank search cannot establish that nobody else wrote similar software.
How long does registration take, and must it be renewed?
We do not give a fixed processing estimate because the office does not publish a reliable service standard for every software filing. Completeness, ownership questions and the suitability of the submitted copy can affect handling. Confirm the current position when filing.
There is no copyright renewal filing. Registration does not start or extend the statutory term; the term comes from Sec. 14 and the applicable category. Our guide to how long copyright lasts in Nepal explains the categories.
How do open-source and third-party components affect a filing?
Most modern programs contain dependencies the applicant did not author. Make a software bill of materials or equivalent component list, keep the applicable licences, and distinguish those components from the company's original code.
Open-source does not mean “no copyright.” It means the copyright holder grants permissions subject to a licence. Some licences require notices, source availability or compatible distribution terms. A registration claim should not present third-party components as the applicant's own work.
Can a software name or technical invention be protected too?
Yes, through different rights. A product name or logo may be registered as a trademark. Downloadable software commonly raises Class 9 questions, while hosted SaaS and development services may raise Class 42 questions. Classification follows the goods and services actually offered.
A technical solution may deserve a separate patent assessment, but copyright registration says nothing about patentability. Start with our comparison of trademarks, copyright, patents and designs before choosing a filing route.
What evidence should you preserve after registration?
Keep the certificate with the exact submitted copy, its hash, the complete release archive, repository history, signed agreements, component licences and dated publication records. Store access logs and backups in a way that preserves their reliability.
If copying occurs, do not edit the suspected material or rely only on screenshots. Preserve URLs, dates, downloadable builds and lawful comparison evidence, then obtain advice on the response. Our guide to copyright infringement in Nepal outlines the wider framework.
Common mistakes
- Calling the company the author without explaining the individual contributors.
- Filing an unidentified code dump rather than a fixed version.
- Including credentials, customer data or signing material in the copy.
- Claiming open-source dependencies as original company code.
- Relying on an invoice where a written transfer should exist.
- Treating registration as proof of novelty, security or patentability.
- Assuming the certificate covers every later release.
- Discarding the repository and contracts after registration.
What does a careful startup filing look like?
This is an illustration, not a real case. A Kathmandu SaaS company prepares version 3.0 for an investment round. Two founders wrote the first version, an agency rebuilt the mobile client, and employees developed the current server.
The company first signs a written assignment for the founders' pre-company code and checks the agency agreement. It creates a component list, separates third-party packages, freezes the release, removes secrets from the filing copy and records a hash of both the full internal archive and submitted material.
It files the identified version as a copyright record. Separately, it searches and files its product name in the relevant trademark classes. The result is not a promise that no dispute can arise; it is a clean, reviewable evidence trail.
Where can you verify the legal basis?
Read the current Copyright Act through the Nepal Law Commission and verify procedure with the Nepal Copyright Registrar's Office. For international background, the World Intellectual Property Organization explains copyright principles, but Nepal's statute and office practice govern a Nepali filing.
For a practical ownership review, contact IP Sewa with the program type, version, contributor list and available agreements. Questions about a disputed contract or threatened claim should be reviewed by a qualified lawyer.
In short
Software copyright in Nepal is automatic for original protected expression, while registration is a voluntary evidence step. A strong application identifies one build, every contributor, the company's ownership chain and all third-party components without disclosing operational secrets.
Use the Copyright Registrar's Office for code, the Department of Industry for trademarks or a possible patent, and written agreements to connect the creators to the applicant.
People also search for
- What does copyright registration prove in Nepal?
- How does the general copyright registration process work?
- Does a software business need copyright or a trademark?
- How does copyright apply to AI-generated content?
- What does a copyright certificate say?
Need to identify the right filing or clean up the ownership record first? Contact IP Sewa with the release, contributor list and contracts you already have.
Comments (0)
Leave a comment
Replying to — cancel