Software and Code Copyright Protection Under U.S. Law

U.S. copyright law extends to computer software and source code as a category of protectable literary works, a classification that carries significant consequences for developers, employers, open-source contributors, and technology companies. Protection arises automatically upon creation and fixation, but the scope of that protection is shaped by doctrines that distinguish protected expression from unprotectable ideas, functions, and interfaces. This page covers the legal definition of software copyright, how protection operates in practice, the scenarios where disputes most often arise, and the boundaries that courts and the Copyright Office use to determine what is and is not protected.

Definition and Scope

Under 17 U.S.C. § 101, a "computer program" is defined as "a set of statements or instructions to be used directly or indirectly in a computer in order to bring about a certain result." The U.S. Copyright Office classifies software as a literary work for registration purposes, meaning it falls under the same Title 17 protections that govern novels, poems, and other written expression.

Protection covers both source code (human-readable instructions in languages such as C++, Python, or Java) and object code (the compiled, machine-executable binary form). The Copyright Office accepts deposits of source code for registration, though applicants may redact portions they consider trade secrets under 37 C.F.R. § 202.20.

Copyright protection does not extend to:

1. The underlying idea, algorithm, or method of operation (governed by the idea-expression dichotomy)
2. Purely functional elements that have no expressive alternatives
3. Facts, data structures determined entirely by external standards
4. Elements in the public domain or released under permissive licenses

This scope question — what portions of code are expressive versus functional — has been the central battleground in software copyright litigation since at least Whelan Associates, Inc. v. Jaslow Dental Laboratory, Inc. (3d Cir. 1986) and the subsequent Computer Associates International, Inc. v. Altai, Inc. (2d Cir. 1992), which established the abstraction-filtration-comparison (AFC) test still referenced by courts.

How It Works

Automatic Attachment

Copyright protection attaches at the moment original code is written and saved to a fixed medium — no registration, notice, or publication is required under the Berne Convention, which the United States joined in 1989. However, registration with the Copyright Office before infringement occurs, or within three months of first publication, is a prerequisite to filing a federal infringement lawsuit and to claiming statutory damages under 17 U.S.C. § 412.

Registration Mechanics

Software is registered using Copyright Office Form TX (literary works). Applicants deposit identifying material — typically the first and last 25 pages of source code — along with a completed application and the current filing fee ($65 for a single online application as of the Copyright Office's published fee schedule (Copyright Office Fees)). For trade-secret-sensitive code, a "rule of doubt" procedure allows deposit of redacted pages if at least 50% of the code remains visible.

Ownership Defaults

The default copyright owner is the author. When software is created by an employee within the scope of employment, the works-made-for-hire doctrine (17 U.S.C. § 101) vests ownership in the employer automatically. Independent contractor arrangements do not trigger work-for-hire status for software unless a written agreement expressly designates the work as such — software is not among the nine statutory categories listed in § 101(2) that qualify for contractor-based work-for-hire treatment.

Duration

For works created after January 1, 1978, protection lasts for the life of the author plus 70 years (17 U.S.C. § 302). For corporate works made for hire, the term is 95 years from publication or 120 years from creation, whichever expires first. See copyright duration and expiration for the full term table.

Common Scenarios

Employee vs. Contractor Development

A software engineer employed full-time writes a billing module during business hours using company equipment. Under the work-for-hire doctrine, the employer holds the copyright without any written transfer. A freelance developer hired under a services contract to build the same module retains copyright unless the contract contains a valid written work-for-hire or assignment clause — a point litigated in Aymes v. Bonelli (2d Cir. 1992), where the court applied a multifactor test to distinguish employee from independent contractor status.

Open-Source Licensing

Open-source software carries active copyright owned by its contributors. Licenses such as the GNU General Public License (GPL), published by the Free Software Foundation, or the Apache License 2.0 grant broad permissions conditioned on specific obligations (attribution, source disclosure, license compatibility). Violating those conditions reverts the licensee to infringement status — the copyright is not abandoned. The DMCA overview addresses how takedown mechanisms interact with open-source repositories.

API Copyright

The Google LLC v. Oracle America, Inc. (U.S. Supreme Court, 2021) decision held that Google's copying of approximately 11,500 lines of Java API declaring code qualified as fair use, but the Court did not definitively resolve whether APIs are copyrightable in the abstract. The question of API copyrightability remains unresolved as a bright-line rule; the fair use analysis in any given case depends on the four-factor test under 17 U.S.C. § 107. See fair use doctrine for the factor-by-factor framework.

Reverse Engineering

The DMCA's anti-circumvention provisions (17 U.S.C. § 1201) restrict bypassing technological protection measures (TPMs), but § 1201(f) provides a narrow exemption for reverse engineering undertaken solely to achieve interoperability with an independently created program. The Copyright Office conducts triennial rulemaking to define additional exemptions; the anti-circumvention provisions page covers the rulemaking cycle in detail.

Decision Boundaries

Courts and the Copyright Office apply the following distinctions to determine whether a software element qualifies for protection:

Idea vs. Expression
The idea-expression dichotomy bars protection for the concept behind a program — a sorting algorithm as an abstract idea — while protecting the specific code implementing it. The more functional a software element, the closer it sits to the unprotectable "idea" pole.

Merger Doctrine
When an idea can be expressed in only one or a very limited number of ways, the expression "merges" with the idea and loses copyright protection. Applied to software, if there is only one efficient way to implement a given function in a given language or environment, that implementation is unprotectable regardless of originality.

Scenes à Faire
Elements that are standard, expected, or dictated by external factors — error messages following industry conventions, file structures required by an operating system, or variable names mandated by hardware interfaces — are excluded from protection under the scenes à faire doctrine.

Originality Threshold
Copyright requires only a minimal degree of creativity (Feist Publications, Inc. v. Rural Telephone Service Co., 499 U.S. 340 (1991)). Purely mechanical or formulaic code — boilerplate library calls, auto-generated scaffolding — may fail this threshold, though the bar is low.

Functional vs. Expressive Output
A program's audiovisual output (screen displays, icons, user interface elements) may carry its own copyright separate from the underlying code, as established in Stern Electronics, Inc. v. Kaufman (2d Cir. 1982). The output copyright and the code copyright are distinct and may be owned by different parties.

Copyright vs. Patent vs. Trade Secret
Copyright protects expression in code; patents protect novel, non-obvious functional processes or machine implementations (USPTO); trade secret law protects confidential information with commercial value from misappropriation. These three regimes overlap for software but serve different purposes and require different legal strategies. The copyright vs. trademark vs. patent page maps the boundaries among all three intellectual property regimes.

For remedies available when software copyright is infringed — including statutory damages ranging from $750 to $150,000 per work under 17 U.S.C. § 504 (Copyright Office, Circular 99) — see copyright remedies and damages and statutory damages copyright.

References

• U.S. Copyright Office — Computer Programs (Circular 61)
• 17 U.S.C. Title 17 — Copyrights, full text
• 37 C.F.R. § 202.20 — Deposit of Copies for Registration
• [U.S. Copyright Office — Fee