Copyright for Software Startups: What It Covers
Yes. In the US, source code is protected by copyright automatically the moment you write it, with no filing needed. Copyright covers the code as written (and its visible expression), not the underlying idea or how the software works. Registration is optional but is generally required before you can sue, and it affects what damages you can recover.
Startup lifecycle A to Z · Letter C · Stage: Build
Is source code copyrighted?
Yes. US copyright law treats software as a kind of written work. Copyright attaches automatically when an original piece of writing is fixed in some lasting form, such as saved to a file. You do not need to file anything, add a notice or pay anyone for the protection to exist. If you write an original program, you (or the company that owns your work) hold copyright in it from the moment it is saved.
The question founders should really ask is not "is my code protected?" but "what exactly is protected, and who owns it?" Those two questions drive most of the practical decisions below.
What copyright protects in software
- The source code, as the specific text you or your team wrote.
- The compiled object code produced from it.
- Original written material around the product, such as documentation, help text and marketing copy.
- Original visual material, such as illustrations, icons you drew and the creative look of a screen, to the extent it is original expression.
- Original database structure or selection in some cases, though the rules here are narrower and worth asking an attorney about.
What copyright does not protect
Copyright protects expression, not ideas. That single distinction explains most of what founders find surprising.
- Ideas, concepts and business methods. Nobody owns the idea of a ride-sharing app or a budgeting tool.
- How the software works. Functionality, algorithms and methods of operation are not covered by copyright, though they may be candidates for a patent or a trade secret.
- Facts and data. Raw facts are generally not protected, even if collecting them took real effort.
- Short names and slogans. Your product name is a trademark question, not a copyright one.
- Standard, obvious or functionally dictated code. Where there are only a few sensible ways to write something, the law tends to give it little or no protection.
The practical result: a competitor who studies how your product behaves and writes their own code from scratch usually has not infringed your copyright. A competitor who copies your files, or a close paraphrase of them, may have. Copyright is strong against copying and weak against independent re-creation.
Copyright vs patent for software
Founders often use "protect my software" to mean one thing, but copyright, patents and trade secrets each protect a different layer. They can be used together.
| Question | Copyright | Patent | Trade secret |
|---|---|---|---|
| What it protects | The code and other creative expression as written | A new, useful, non-obvious invention, including how something works | Confidential information with business value |
| How you get it | Automatically on creation | You apply, and an examiner decides | Automatically, if you keep it secret and take reasonable steps |
| Public record? | Registration is optional; registered deposits can be limited | Yes, applications generally publish | No, secrecy is the point |
| Stops independent creation? | No | Yes, within the claims | No |
| Typical duration | Many decades (see the Copyright Office) | Generally up to 20 years from filing | As long as it stays secret |
For most software startups, copyright is the baseline layer you already have, and a trade secret is the layer you protect with process. Patents are a deliberate, expensive choice that fit only some products, and software eligibility for patents is a difficult area. If you are weighing that choice, read do I need a patent for my app. For a broader comparison, see patent vs trade secret for startups. The USPTO also publishes a short explainer on the differences between trademarks, patents and copyrights.
Should I register copyright for my app?
Registration is optional. Your copyright exists without it. But for a US work, registration (or a decision by the Copyright Office on your application) is generally a precondition to filing an infringement lawsuit in federal court. It also affects the remedies available.
Why founders choose to register
- You can sue. Without registration, a US author generally cannot bring an infringement suit for the work.
- Statutory damages and attorney's fees. These are generally available only if the work was registered before the infringement began (or within a short window after first publication). Without them, you must prove your actual losses, which can be hard for an early product.
- A public, dated record of ownership. This can help in a dispute and can reassure a buyer or investor doing diligence.
Why many startups wait
Software changes constantly. A registration covers a specific version of the work, so a product shipping weekly raises the question of which version to register and how often. Registration also has a cost and takes some effort, and your product may never face a copying dispute. Many founders register a significant release of the core product, or the version they would most hate to see copied, rather than every commit. Whether and when to register is a judgment call to make with an attorney, and current fees are on the Copyright Office website.
What registration involves, in outline
- Confirm who the author or claimant is. If employees or contractors wrote the code, ownership must be clean first (see the next section).
- Decide which version of the work to register.
- Prepare the deposit, which is generally identifying portions of the source code. The Copyright Office has rules that let applicants limit or redact portions containing trade secrets, so you do not have to hand over everything. Check its current guidance on software deposits.
- File the application with the Copyright Office and pay the fee.
- Keep the certificate and the exact version you registered in your records.
Registration is separate from patents and from trademarks. If your product name matters, that is a different filing; see how to trademark your startup name.
Who owns the code? Employees, founders and contractors
This is where startups most often get hurt. Copyright starts with the person who actually wrote the code, the author. Ownership moves to someone else only in specific ways.
Employees and work made for hire
Under US copyright law, a work created by an employee within the scope of their job is a "work made for hire," and the employer is treated as the author. That is why code written by your salaried engineers as part of their jobs generally belongs to the company. Still, most companies also put a written invention and confidentiality agreement in place, because "employee" and "scope of employment" can be disputed, and because it also covers patents and trade secrets. See IP assignment agreements for startups.
Independent contractors and freelancers
Contractors are different. The default rule is that a freelancer who writes code owns the copyright in it, even though you paid for it. You get at most an implied license to use what you paid for, and an implied license can be narrow and uncertain.
The "work made for hire" label does not reliably fix this for software. For a commissioned (non-employee) work to qualify, it must fall into one of a short list of categories in the statute, and there must be a signed written agreement saying it is a work made for hire. Whether a given piece of software fits one of those categories is often unclear. For that reason, the safer practice many attorneys follow is to have the contractor sign a written assignment of copyright (a transfer of ownership), sometimes combined with work-made-for-hire wording. A transfer of copyright ownership generally must be in writing and signed by the person giving it up. Ask an attorney to draft this and to confirm what works in your state.
Co-founders and pre-incorporation code
If a founder wrote code before the company existed, that founder personally owns it until they transfer it. Do this at or soon after formation, in writing. It is also a topic for your co-founder equity discussion, since founders are often assigning IP in exchange for their shares. See the startup legal checklist for where this sits among other early tasks.
Open source license basics for startups
Nearly every modern codebase includes open source code. Open source does not mean ownerless. The authors keep their copyright and grant you permission to use the code under a license. If you break the license terms, you may lose that permission.
The two broad families
| Type | Typical examples | General idea |
|---|---|---|
| Permissive | MIT, BSD, Apache 2.0 | Use it in commercial, closed products if you keep the required notices. Apache 2.0 also includes an express patent license. |
| Copyleft | GPL, LGPL, AGPL | If you distribute (or, under the AGPL, in some cases offer over a network) software combining the code, you may have to make your own source available under the same terms. |
Which obligations are triggered depends on the exact license, version and how you combine and ship the code. That is a legal judgment, not something to guess at.
A working discipline
- Keep an inventory. List the open source components you use and each one's license. Dependency scanning tools can produce this list.
- Set a simple policy. Decide in advance which licenses engineers may use without asking, and which need approval.
- No license is not free. Code posted publicly with no license is generally not licensed for you to reuse. Treat it as off limits unless you get permission.
- Check before you raise or sell. Investors and acquirers often ask how open source is managed. See protecting IP before fundraising.
Also decide the reverse question: if you plan to release your own code as open source, you are choosing a license for it. That choice is hard to undo for code already released, so settle it before you publish.
Common mistakes with software copyright
- Assuming a paid freelancer gives you ownership. Without a signed assignment, they may own what they wrote.
- Relying on a handshake or an email thread for ownership transfer.
- Copying code from forums, tutorials or AI tools without checking the license or terms that apply. Whether and how copyright applies to machine-generated output is an evolving question; ask an attorney and check the Copyright Office's guidance.
- Pasting copyleft code into a closed product without reading the license.
- Believing that a copyright notice or a registration stops competitors from building a similar product. It does not; it addresses copying of expression.
- Waiting until a funding round to find out who wrote what.
A software copyright checklist
- List every person who has written code, designs or documentation for the product, and mark each as employee, contractor or co-founder.
- Confirm each has signed a written agreement assigning ownership to the company.
- Fix the gaps now. Getting a signature from a former contractor later is harder and sometimes costs money.
- Inventory open source components and their licenses.
- Add a copyright notice (the symbol, year and owner) to your source files and app. It is not required, but it removes an excuse for infringement.
- Decide with an attorney whether, when and which version to register.
- Keep your repository history and records of who contributed what.
When to talk to an attorney
Get a copyright or IP attorney involved for contractor assignment language, for any open source question that affects how you distribute the product, and before registration if the code contains trade secrets. If the product might be patentable, a registered patent attorney or agent is a different specialist; see patent attorney or agent for startups. This guide is general education about US law, not legal advice for your situation, and rules outside the US differ.
Frequently asked questions
Is source code copyrighted automatically?
In the US, yes. Original source code is protected by copyright as soon as it is written and saved in some lasting form. You do not need to register it or add a notice. Registration is a separate, optional step that matters mainly if you ever need to sue or want certain remedies.
Do I need to register copyright to protect my app?
No, the protection exists without registration. But a US author generally has to register before filing an infringement lawsuit, and registering early can make statutory damages and attorney's fees. Whether it is worth it for your app is a judgment call to discuss with an attorney.
Does copyright stop someone from copying my app's features?
Usually not. Copyright protects the code and creative expression, not the ideas or functions behind them. A competitor who writes their own code to do the same thing has generally not infringed. Patents or trade secrets address how something works, in different ways.
Who owns code written by a freelancer?
By default, the freelancer generally owns the copyright, not the company that paid. To own it, you typically need a signed written agreement that assigns the rights to you. Have an attorney draft it, because work-made-for-hire status often does not apply cleanly to commissioned software.
Can I use open source code in a commercial product?
Often yes, but each license has conditions. Permissive licenses like MIT usually require keeping notices. Copyleft licenses like the GPL can require you to share your own source in some situations. Read the specific license and get legal advice if you distribute or host the combined software.
What is the difference between copyright and a patent for software?
Copyright protects the code as written and arises automatically. A patent protects an invention, meaning how something works, but requires an application and examination, and software eligibility is a difficult area. A patent can stop others even if they write their own code; copyright generally cannot.
Key terms on this page
Keep reading
- IP Assignment Agreements for Startups Explained IP guideIP assignment agreement basics for startups: founder IP assignment, invention assignment for employees, contractor IP ownership and what to include.
- Do I Need a Patent for My App? A Founder's Guide IP guideDo I need a patent for my app? Learn what software patents cover, why eligibility is a hard question, and what protects an app without one.
- Patent vs Trade Secret: Which Fits Your Startup? IP guidePatent vs trade secret for startups: how each works, how long they last, the patent disclosure requirement, and how to decide, including for software.
- Trade Secrets for Startups: NDAs and Secrecy Steps IP guideTrade secrets for startups: what qualifies, what reasonable secrecy measures look like, when to use an NDA, and whether investors will sign one.
- Startup Legal Checklist: What to Handle Early GuideStartup legal checklist for first-time founders: entity, founder agreements, IP, EIN, licenses, contracts and privacy. A starting point for an attorney talk.
Learn more from Wysebridge
Wysebridge owns, operates and sponsors Revolutionary Startups, so these are links to its own free resources and directories. Read the disclosure.
- Wysebridge copyright law guideFree guide to what copyright protects, registration, fair use, work made for hire and the DMCA.
- Wysebridge IP law in the age of AI courseHow generative AI affects copyright, patent, trademark and trade secret law, in 18 chapters.
- Wysebridge U.S. IP law courseA 20-chapter self-study course on U.S. patent, trademark, copyright and trade secret law; module 1 is free.
Part of IP for founders · All guides · Glossary
Sources
- U.S. Copyright Office: How long does copyright protection last?
- USPTO: Trademark, patent, or copyright?
General information, not legal, tax or financial advice. Reviewed 11 November 2026.