Software Copyright Protection in Japan: Program Works, Registration and Patents

How Japan treats software as a copyright work

Japanese copyright law protects computer programs as a recognised category of work, usually referred to as program works. A program work is the expression of the code you have written, and protection attaches automatically the moment the work is created. You do not file anything, pay anything or mark the code in any particular way to hold the copyright. This mirrors the position across most of the Japanese copyright landscape, where authorship rights arise on creation rather than on registration.

What copyright protects is the expression: the particular way the source and object code are written. It does not protect the ideas underlying that expression, and Japanese law is explicit that certain things are outside program-work protection, namely programming languages, rules or conventions (including interface specifications) and algorithms. The concrete code that implements an interface can still be protected, but the underlying convention or protocol is not. Two developers who independently write different code to solve the same problem each hold copyright in their own work, and neither infringes the other. That distinction between protected expression and unprotected idea is central to any software protection strategy in Japan, because it shapes what copyright can and cannot stop a competitor from doing.

The voluntary registration option

Although copyright needs no registration to exist, Japan operates a voluntary registration system for program works. Registration does not create the right; the right is already yours. Its most distinctive feature is registration of the date of creation, which carries a legal presumption that the program was created on the registered date. That presumption is unique to program works and can be valuable if ownership or timing is ever disputed. A limited window applies for registering the date of creation, so confirm the current position with the Agency for Cultural Affairs or local counsel rather than relying on a fixed figure.

Program works are registered with a designated registration organisation, not directly with the Agency for Cultural Affairs itself (general, non-program copyright registrations are made with the Commissioner of the Agency). The designated organisation for program registration is the Software Information Center, commonly known as SOFTIC, and it currently handles this function under the supervision of the Agency for Cultural Affairs. Official fees apply, so confirm the current amount with the Agency for Cultural Affairs or local counsel; timescales and procedural steps also change over time, so treat any figure you read online as indicative and verify the current position before you rely on it.

Registration is worth considering when the software is commercially significant, when you expect licensing or investment due diligence, or when you want an official record of authorship and creation date to fall back on. For lower-value or fast-moving code, many businesses rely on the automatic protection alone and keep good internal records of development history instead. The right choice depends on the value at stake and your appetite for evidencing ownership, which is a conversation to have with a qualified adviser rather than a fixed rule.

Copyright and patents working together

Copyright and patents protect different things, and in software they often work best in combination. Copyright protects the expression of your code. A patent, by contrast, can protect the underlying technical invention: a novel and inventive technical method or process that the software implements. If your product depends on a genuine technical advance rather than only on the way the code is written, a patent may reach protection that copyright cannot, because a competitor who reimplements the same technical idea in entirely different code would not infringe your copyright but could infringe a patent.

Not all software is patentable, and the requirements are demanding. The invention must clear novelty and inventive-step thresholds and be framed as a technical solution rather than an abstract idea or pure business method. Our guide to software and AI patents in Japan sets out how the Japan Patent Office approaches computer-implemented inventions and where the line tends to fall. A layered strategy, copyright on the expression as a baseline, a patent where a real technical invention justifies the cost and disclosure, plus clear contracts and confidentiality around your code, generally gives a software business the most durable position.

Ownership is the other half of the picture, and Japan draws an important line between employees and contractors. For a program created by an employee in the course of their duties, the default rule vests authorship in the employer, so the business will usually hold the rights without needing a separate assignment. Independent contractors and freelancers are different: absent an assignment, the copyright stays with the creator, so your agreements must license the resulting rights clearly or, better, assign the economic copyright outright. Moral rights need separate handling, because in Japan an author's moral rights cannot be assigned. They are personal to the author, so they are usually dealt with by a non-assertion agreement in which the author agrees not to exercise them, rather than by transfer. Getting the economic assignment and the moral-rights position documented at the outset avoids expensive uncertainty later.

Where to go next

This page is general information and not legal advice. IPEnvoy is not a law firm and does not provide legal advice; confirm the current position with the Agency for Cultural Affairs and a qualified local IP professional before you act. If you would like help mapping your software portfolio to the right mix of copyright, registration and patents in Japan, IPEnvoy can connect you with vetted local IP counsel to review your specific situation and take it forward.