Software licenses and copyright work as a pair: copyright automatically gives a developer exclusive control over their code the moment it’s written, and a license is the legal document that lets someone else use that code under defined conditions. Copyright is the source of the rights; the license is how those rights get shared. Mixing the two up is how individuals and companies end up infringing without meaning to.
What Copyright Protects in Software
Copyright attaches to original code the instant it’s saved to a file. No registration, no notice, no filing is required. Both the human-readable source code and the compiled version a computer runs are covered. Federal law gives the copyright holder exclusive rights to copy the work, distribute it, and build new versions based on it.1Office of the Law Revision Counsel. 17 USC 106 – Exclusive Rights in Copyrighted Works
What copyright doesn’t protect is the underlying idea. You can’t copy someone’s code, but you can study what their program does and write your own version from scratch. Algorithms, mathematical methods, and functional concepts are all fair game. Protection covers how something is expressed in code, not what the code accomplishes. That’s the principle that keeps the market competitive: ten developers can build ten spreadsheet programs so long as each writes original code.
Courts have sometimes extended protection past literal code to a program’s structure and organization, but the boundaries are unsettled. In 2021, the Supreme Court held in Google LLC v. Oracle America that Google’s use of roughly 11,500 lines of Java API declarations (about 0.4% of the total API) to build Android was fair use, partly because the copied code served as a functional interface programmers had already spent years learning.2Supreme Court of the United States. Google LLC v. Oracle America, Inc. Functional, interface-level code gets weaker protection than purely creative expression. If you’re building software that has to interoperate with another system, that distinction matters.
Fair Use and Backup Rights
Copyright’s exclusive rights aren’t absolute. Fair use allows limited copying without permission for purposes like research, criticism, and education. Courts weigh four factors together: the purpose of the use, the nature of the work, how much was copied relative to the whole, and the effect on the market for the original.3Office of the Law Revision Counsel. 17 US Code 107 – Limitations on Exclusive Rights: Fair Use For software, fair use has been used to justify reverse engineering for interoperability when there’s no other way to reach the unprotected functional elements.
If you own a legitimate copy of a program, federal law also gives you two specific rights: you can make an archival backup, and you can make whatever adaptations are needed to actually run the software on your machine.4Office of the Law Revision Counsel. 17 US Code 117 – Limitations on Exclusive Rights: Computer Programs These rights belong to owners of copies. Most proprietary licenses say explicitly that you’re a licensee, not an owner, which can knock out this protection.
How a Software License Works
A software license is a permission slip. Because copyright gives the developer exclusive control over copying and distribution, anyone who installs, copies, or runs the software needs the developer’s permission. The license grants that permission on specific conditions without transferring the copyright itself. It’s closer to a lease than a sale.
Every time you click “I Agree” during installation, you’re entering into one of these agreements. The terms dictate what you can do with the software, how many devices you can install it on, and what happens if you break the rules. Click-through agreements (sometimes called clickwrap contracts) are routinely enforced by courts.
How Cloud Software Changes the Model
The traditional license assumed you’d download and install software on your own computer. Cloud-based software, usually called Software as a Service (SaaS), works differently. You never receive a copy of the program. You access the application through a web browser while the provider runs everything on their servers. The governing document is typically a Terms of Service agreement rather than a traditional license, because the provider is delivering access to a service rather than granting permission to use a copy.
The practical difference is real. With installed software, revoking your license is hard to enforce because you already have the files. With SaaS, the provider can cut off your access instantly. SaaS agreements also tend to give the provider more freedom to change terms, update the software, or discontinue features without your consent. If your business depends on a SaaS product, read the data portability and termination clauses closely.
Common Types of Software Licenses
Licenses vary widely, but most fall into a few recognizable categories.
Proprietary Licenses
Proprietary licenses are the most restrictive. The developer keeps the source code secret, and you only interact with the compiled version. The End-User License Agreement (EULA) typically prohibits reverse engineering, modification, and redistribution. You’re paying for the right to use the software on the developer’s terms. Microsoft Windows and Adobe Photoshop are familiar examples.
Permissive Open Source Licenses
Permissive open source licenses like the MIT License and Apache License 2.0 go in the opposite direction. They make the source code available for anyone to inspect, modify, and redistribute. The MIT License grants permission to use, copy, modify, and sell the software with essentially one condition: you include the original copyright notice and permission notice in any copies.5Open Source Initiative. The MIT License The Apache License adds a few more requirements, including explicit patent rights and attribution notices, but still lets you fold the code into proprietary products.6Apache Software Foundation. Apache License, Version 2.0
Copyleft Licenses
Copyleft licenses, most famously the GNU General Public License (GPL), take a different philosophical approach. They make the source code available and let you modify it freely, with a catch: if you distribute a modified version, you must release your version under the same license. The GPL requires that anyone receiving a copy also receives the freedom to inspect, modify, and redistribute it.7GNU Project – Free Software Foundation. What is Copyleft? This prevents companies from taking open source code, improving it, and locking the improvements behind a proprietary license. For businesses, this “viral” quality is worth thinking through before pulling GPL-licensed code into a product you plan to sell.
Creative Commons Is Not for Code
Developers sometimes put a Creative Commons license on their code. Creative Commons itself recommends against this. Their licenses don’t address source code distribution, don’t handle patent rights, and aren’t compatible with established open source licenses like the GPL or MIT License.8Creative Commons. Frequently Asked Questions Use CC licenses for documentation, artwork, or media assets. Use a recognized open source license for code.
Clauses to Read Before You Agree
Whether a license is proprietary or open source, certain clauses show up over and over. Knowing what they mean keeps you from agreeing to something that will bite you later.
- Scope of use defines exactly what you’re allowed to do. Common restrictions include limiting installation to a single device, prohibiting commercial use, or capping use to a set number of employees. Some licenses also bar using the software to build a competing product.
- Distribution and modification rights say whether you can share the software or alter its code. Proprietary licenses almost always deny both. Open source licenses grant both, often with attribution or share-alike conditions.
- Warranty disclaimers state the software is provided “as is.” The developer makes no promise it will work perfectly or be free of bugs, and the risk of defects shifts to you.
- Limitation of liability caps the developer’s financial exposure if the software damages your data or systems. Many licenses limit liability to what you paid for the software, and some exclude indirect or consequential damages entirely.
- Audit rights, common in enterprise licenses, let the vendor inspect your systems to check compliance, typically once a year with 30 days’ notice. If an audit shows you’re running more copies than you’ve paid for, you’ll owe back-licensing fees and possibly penalties.
Who Owns Code Written for a Business
The default rule is simple: the person who writes the code owns the copyright. In a business context, that default almost never applies because of the work-made-for-hire doctrine.
When an employee creates software within the scope of their job, the employer is treated as the legal author and owns the copyright automatically. No contract or assignment is needed.9Office of the Law Revision Counsel. 17 US Code 201 – Ownership of Copyright Independent contractors are different. Software created by a freelance developer does not automatically qualify as a work made for hire, because “computer program” isn’t one of the categories eligible for that treatment under the statute’s definition.10Office of the Law Revision Counsel. 17 US Code 101 – Definitions
This catches companies off guard constantly. You pay a contractor $50,000 to build a custom application, and unless there’s a written assignment transferring the copyright to you, the contractor still owns it. Federal law requires any transfer of copyright ownership to be in writing and signed by the person giving up the rights.11Office of the Law Revision Counsel. 17 US Code 204 – Execution of Transfers of Copyright Ownership A verbal agreement won’t hold up. If you’re commissioning software development, the copyright assignment clause isn’t boilerplate to skim.
Why Registration Matters for Enforcement
Copyright exists without registration, but enforcing it in court requires one. You cannot file a federal infringement lawsuit over a U.S. work until the Copyright Office has either granted or refused your registration application.12Office of the Law Revision Counsel. 17 US Code 411 – Registration and Civil Infringement Actions Submitting the application isn’t enough; the office has to act on it.
Timing matters even more. To be eligible for statutory damages and attorney’s fees, you need to register before the infringement begins, or within three months of first publishing the work.13U.S. Copyright Office. Chapter 4: Copyright Notice, Deposit, and Registration – Section 412 Miss that window and you’re limited to proving your actual financial losses, which for software can be difficult and expensive to calculate.
Penalties for License Violations and Infringement
Using software outside the boundaries of its license exposes you to both contract and copyright liability. The copyright holder can terminate your license, and any continued use after termination is straightforward infringement.
Civil Damages
A copyright holder can elect to recover statutory damages instead of proving actual losses. The range is $750 to $30,000 per infringed work at the court’s discretion. If the court finds the infringement was willful, the ceiling jumps to $150,000 per work.14Office of the Law Revision Counsel. 17 USC 504 – Remedies for Infringement: Damages and Profits “Per work” is the key phrase. A company running unlicensed copies of five different programs faces separate exposure on each one. Statutory damages and attorney’s fees, again, are only available if the copyright was registered before the infringement started or within three months of publication.13U.S. Copyright Office. Chapter 4: Copyright Notice, Deposit, and Registration – Section 412
Criminal Penalties
Willful infringement for commercial gain, or involving copies worth more than $1,000 in retail value, can trigger criminal prosecution.15Office of the Law Revision Counsel. 17 US Code 506 – Criminal Offenses Reproducing or distributing at least 10 copies of copyrighted works with a total retail value exceeding $2,500 within a 180-day period carries up to five years in prison for a first offense, with fines set under Title 18’s general provisions (up to $250,000 for individuals). Second offenses can double the prison time to ten years.16Office of the Law Revision Counsel. 18 USC 2319 – Criminal Infringement of a Copyright
Bypassing Digital Locks
Federal law separately makes it illegal to bypass technological protection measures (DRM, license key systems, copy protection) that control access to copyrighted software, even if the underlying use might otherwise be lawful.17Office of the Law Revision Counsel. 17 US Code 1201 – Circumvention of Copyright Protection Systems Cracking a program’s activation system to avoid paying for a license is a separate violation on top of the infringement itself. The Librarian of Congress grants narrow exemptions every three years for specific classes of works, but those exemptions are limited and don’t give a blanket right to circumvent protections on commercial software.
Time Limits on Lawsuits
A copyright holder has three years from when a claim accrues to file a civil infringement lawsuit. Older infringement isn’t automatically consequence-free, though: ongoing infringement, such as continuing to use unlicensed software, can restart the clock, and the three-year window applies separately to each act.
Where Patents Fit In
Copyright and patents protect different aspects of software, and confusing them leads to bad decisions. Copyright protects the specific code as written. A patent protects the functional invention itself, the underlying method or process, regardless of how it’s coded. If you write your own original code that performs a patented process, copyright won’t help you: the patent holder can still sue.
Getting a software patent is much harder than getting copyright protection. The invention must be new, not obvious, and must clear a significant legal hurdle: it can’t just be an abstract idea implemented on a computer. The Patent Office applies a two-step test asking whether the claim is directed at an abstract concept and, if so, whether it adds something “significantly more” than the abstraction itself.18USPTO. Patent Subject Matter Eligibility Many software patent applications fail there. For most independent developers, copyright provides enough protection. Patents become relevant primarily when the innovation lives in the method rather than in the code that implements it.