In almost every country, software is automatically owned by its author at the time it is created. The author can then choose to grant rights to others under copyright law in their respective country. This principle of automatic ownership was enshrined in most parts of the world by the Berne Convention and is essential to ensure consistent license interpretation across jurisdictions. Ideas for how to create software or how it should function are generally not copyrightable — the author only has rights to the actual code. Open Source licenses are powerful in that they allow the author to grant those rights to others, enabling them to legally use, modify, and share the code.
Copyright is a legal framework that protects original works of authorship — including software code — by providing the author exclusive rights over the work unless and until they decide to grant them to others. In the context of software, the author (or copyright holder) has the exclusive legal right to control how the code is used, copied, modified, and distributed. These rights arise automatically upon creation of the work (no registration is required under the Berne Convention). Importantly, copyright protects the expression of ideas (such as the specific code you write), but not the underlying ideas, algorithms, or functional concepts themselves. For example, a particular software program’s source code is protected by copyright, but the general algorithm or technique it implements cannot be copyrighted.
Rights granted by Copyright: The author of a software program is typically the copyright owner and has sole authority to exercise or permit others to exercise the following rights granted by law:
- Reproduction right: The right to make copies of the software (e.g. copying source code or binaries).
- Modification (derivative works) right: The right to create modified versions or adaptations of the software.
- Distribution right: The right to distribute copies of the software to the public (selling, sharing, or licensing).
- Public performance/display rights: For certain types of works, the right to publicly perform or display the work. (These are less directly relevant for software, but could apply to things like software audiovisual outputs.)
These rights enable copyright holders to control their software. Copyright protection is time-limited: under international norms (Berne Convention) the minimum term is the author’s life plus 50 years, and many countries extend that to life plus 70 years or more. (For works made by companies or “works for hire,” the term is often 95 years from publication in the U.S.) After copyright expires, the work enters the public domain.
What Copyright does not protect: Copyright does not protect ideas, methods, or facts. In software, this means copyright won’t protect an abstract algorithm or functionality — only the specific implementation of an algorithm in code is protected. Anyone is free to independently create new code that performs the same function (or to use the idea in a different way) without infringing copyright, as long as they don’t copy the original code. Other forms of intellectual property, like patents, may protect inventive concepts or techniques in software (more on that below); copyright law is limited to the original expression and tangible form of the work.
Interaction with Open Source licensing: By default, all rights are reserved under copyright: no one can legally use, copy, share, or modify your software without permission. This is where Open Source licensing comes in. Open Source licenses work within the copyright framework by granting the users broad permission to use, modify, and redistribute the code, which would otherwise be restricted. In other words, an Open Source license is the author’s way of saying “I give you permission to do X, Y, Z with my copyrighted software.” The author still retains copyright; others receive a license to exercise some of the author’s rights. For example, if you publish code on a public repository (like GitHub or Forgejo) without providing a license, you own exclusive rights to it by default and no one can legally reuse or modify your code. But if you release it under an OSI Approved License (like MIT, Apache 2.0, or GPL), you are explicitly allowing everyone to use your work under certain conditions. This ability to license one’s rights is built into copyright law, and it’s fundamental to Open Source collaboration.
It’s important to note that Open Source licenses can also impose obligations (like requiring attribution or sharing changes under the same license, in the case of copyleft licenses). However, these obligations are generally enforced through copyright law — if someone violates the license terms, they could be infringing the author’s copyright. Thus, licenses are the legal bedrock of Open Source: they provide authors with control over their work and empower them to grant freedoms to others.
