Trademark vs copyright for an app
By BlockchainSignLast updated
An app is not one thing, so it is not protected by one right. The code, the interface, the name and the underlying idea each sit in a different place — and one of them is not protected at all.
Key takeaways
- Copyright covers your source code, interface graphics, text and audio automatically.
- Trademark covers the app's name and icon as brand identifiers — this is what stops copycat listings.
- Neither covers the idea. An app concept is not protectable, however good it is.
The short answer
Copyright protects what you built. Trademark protects what you called it. Nothing protects the idea.
Most founders asking this question are worried about someone copying the concept. That is the one thing IP law will not help with — and understanding why saves a lot of wasted effort.
What copyright covers
Copyright attaches automatically to:
- Source code and object code, as literary works
- Interface graphics, icons and illustrations, as pictorial works
- Text, including onboarding copy and help content
- Sound and music in the app
That is substantial protection against literal copying. Someone who decompiles your binary and ships it has a serious copyright problem.
What copyright does not cover is the functionality. 17 USC 102(b) excludes ideas, procedures, processes, systems and methods of operation. Somebody who looks at your app, understands what it does, and builds their own from scratch has generally not infringed your copyright.
US registration costs roughly $45–$65 and is required before suing. Registering software involves depositing identifying portions of the code; the Copyright Office permits redacting trade secret material.
What trademark covers
The app's name and its icon function as trademarks once you use them in commerce. This is the practically important right for most app businesses, because the real-world harm is usually a confusingly similar listing in the same store — not stolen code.
Registration is $350 per class, and app software typically falls in class 9, with services in class 42 or elsewhere depending on what the app does.
App stores also run their own trademark complaint processes, which move considerably faster than litigation and are the practical remedy for a copycat listing.
Side by side
| Copyright | Trademark | Patent | |
|---|---|---|---|
| Code | Yes | No | No |
| Icon and graphics | Yes | Yes, as a mark | No |
| App name | No | Yes | No |
| Look and feel | Partly | Sometimes as trade dress | No |
| How it works | No | No | Possibly |
| The idea | No | No | No |
| Cost | ~$45–$65 | $350 per class | Thousands |
| Arises | Automatically | On use in commerce | On grant |
The idea problem
There is no way to own an app idea. Not with an NDA alone, not with a "poor man's copyright", not by emailing yourself the concept.
What you can do is protect the execution — the code, the brand, the data, the relationships — and move quickly. If the idea is genuinely novel as a technical method, a patent may be available, though software patents are expensive and hard to obtain.
If you must disclose a concept before you can protect it, the tool is a contract: an NDA with a party who has a reason to sign one. See how to protect an idea for the realistic version of this.
Where a timestamp fits
Two specific uses for app developers.
Release records. Timestamping a build artefact or a source archive at each release gives you a dated, tamper-evident record of exactly what shipped when. That is useful in an infringement claim, and equally useful in defending one.
Pre-disclosure records. Before pitching to an investor, an accelerator or a potential partner, a timestamp of the design documents and prototype fixes what you had going in.
It records existence and integrity, not authorship or invention. It is not a patent and not a substitute for registration.
US law. This is general information, not legal advice.