You shipped a product. People are using it. Someone on Hacker News mentioned it by name. And now you're wondering: should you trademark it?
Short answer: probably yes. Getting a trademark for software is the same basic process as any other trademark, but with specific traps around classification and naming that catch developers. Most guides on the topic are written for lawyers. This one is written for you.
What a Software Trademark Actually Protects
First, the distinction that trips up every technical founder: a trademark doesn't protect your code. Copyright does that automatically the moment you write it. A patent protects an invention (a novel algorithm, a unique process). A trademark protects the name and logo you use to sell your software.
If you built a project management tool called "Vectra," the trademark covers "Vectra" as applied to project management software. It doesn't stop someone from building a competing tool. It stops them from calling their competing tool "Vectra" (or "Vectra," "Vektra," or anything confusingly similar) in the same product category.
Why does this matter for developers? Because your product name is probably your most important business asset after the code itself. If someone registers your name first, you have two options: rebrand or fight. Rebranding an established product costs real money. Fighting costs more. A trademark registration costs $250-$350 in filing fees.
The math is not complicated.
Which Trademark Class Covers Your Software?
This is where software gets tricky. The trademark system uses Nice classification, an international system that divides all goods and services into 45 classes. Software falls into two:
Class 9: Downloadable software. Mobile apps, desktop applications, firmware, downloadable tools. If a user installs something on their device, it's Class 9. The goods description typically reads something like: "Downloadable computer software for [what your software does]."
Class 42: Software as a Service. Cloud applications, SaaS platforms, hosted services. If your product runs on your servers and users access it through a browser or API, it's Class 42. The services description reads: "Providing temporary use of online non-downloadable software for [what your software does]."
When you need both. Many modern products have both a downloadable component and a cloud component. A code editor with a desktop app and cloud sync needs both Class 9 and Class 42. Each class is a separate filing with its own fee ($250-$350 per class), so two classes means $500-$700 in fees.
A common mistake: filing only in Class 9 when your product is actually SaaS. If your users never download anything, Class 9 doesn't apply. Filing in the wrong class leads to an office action, which means delays, additional fees, and potentially a rejected application.
Not sure which class fits? Read the descriptions carefully. If your product is purely browser-based, it's Class 42. If it's purely downloadable, it's Class 9. If it's both, file both. When in doubt, consult a trademark attorney. The filing fee you save by guessing wrong is nothing compared to the cost of starting over.
How to Register a Trademark for Software, Step by Step
The full registration process from "I should probably trademark this" to a registered mark takes 12-18 months if nothing goes wrong. Here are the steps specific to software.
Step 1: Run a Clearance Search
Before you file anything, check whether your name is available. This is the step most developers skip, and it's the step that causes the most expensive problems.
A clearance search means checking whether anyone else has already registered (or applied for) a similar name in a related class. "Similar" doesn't just mean identical. It includes phonetic equivalents, misspellings, and names with similar meaning. "Vectrix" would likely conflict with "Vectra" in Class 9. "ByteFlow" might conflict with "ByteStream" depending on how similar the products are.
You can start with a free search on the USPTO's Trademark Search system. But a proper clearance search also checks state registrations, common law use, and domain names. Many practitioners recommend a comprehensive search service for applications you care about.
Step 2: Choose Your Filing Basis
The USPTO offers two filing bases for new applications:
Section 1(a): Use in commerce. You're already using the mark in commerce. You have a live product, customers are paying, or you've shipped. You'll need a "specimen" proving use, which is typically a screenshot of your product or website showing the name in connection with the goods/services. For software, an app store listing, a SaaS landing page, or a product screenshot with the name visible all work.
Section 1(b): Intent to use. You haven't launched yet but plan to. This lets you reserve the name while you build. The catch: you'll need to file a Statement of Use (additional ~$150 fee) before the registration issues, and you have a limited window to prove you've started using the mark. If you never use it, the application dies.
For most developers with a shipped product, Section 1(a) is the straightforward choice. If you're pre-launch and want to lock down the name, 1(b) gives you a priority date.
Step 3: File the Application
File through the USPTO's TEAS (Trademark Electronic Application System). You have two options:
- TEAS Plus ($250/class): Cheaper, but you must select your goods/services description from a pre-approved list. Works fine for standard software descriptions.
- TEAS Standard ($350/class): More expensive, but you can write a custom goods/services description. Use this if your software doesn't fit neatly into the pre-approved categories.
For most software trademark registration applications, TEAS Plus works. The pre-approved list includes descriptions for mobile apps, SaaS platforms, and most common software categories.
The application asks for: your name and address, the mark (your product name), the class(es), a goods/services description, a specimen (for 1(a) filings), and the filing fee.
Step 4: Examination
About 3-4 months after filing, a USPTO examining attorney reviews your application. They check whether the mark is registrable (not too descriptive, not confusingly similar to existing marks, not generic) and whether your goods/services description is acceptable.
About 45% of applications receive an office action, meaning the examiner found an issue. Common issues for software applications:
- Goods/services description is too broad or too vague
- Mark is "merely descriptive" of the software's function
- Likelihood of confusion with an existing registration
You have six months to respond to an office action. Most are fixable. Some require a trademark attorney.
Step 5: Publication for Opposition
If the examiner approves your application (or you successfully respond to an office action), the mark is published in the Official Gazette for 30 days. During this window, anyone who believes they'd be harmed by your registration can file an opposition.
Oppositions are relatively rare for software trademarks unless your name is genuinely close to an established brand. If no one opposes, you proceed to registration.
Step 6: Registration
For Section 1(a) filers: your registration certificate issues. You now have a federally registered trademark. You can use the (R) symbol.
For Section 1(b) filers: you receive a Notice of Allowance. You then have six months (extendable) to file a Statement of Use proving you've started using the mark in commerce, plus the ~$150 fee. Once accepted, your registration issues.
Total timeline: 12-18 months from filing to registration if there are no office actions or oppositions. Add 3-6 months if you receive an office action. Add more if there's an opposition.
The Three Mistakes That Sink Software Trademark Applications
I've seen hundreds of software trademark applications. These three mistakes account for most of the failures.
1. Filing in the Wrong Class
Developers build SaaS products and file in Class 9 because "it's software." Class 9 is for downloadable software. If users access your product through a browser and nothing installs on their device, you need Class 42.
Filing in the wrong class triggers an office action. You can amend, but only to narrow the description, not expand it. If you filed in Class 9 for a SaaS product, you can't switch to Class 42 in the same application. You'd need a new filing, which means new fees and losing your original filing date.
2. Choosing a Descriptive Name
This is the hardest lesson for developers. Names that clearly describe what software does are often unregistrable as trademarks. "CodeAnalyzer," "DataSync," "CloudBackup" are all likely to be refused as merely descriptive.
The trademark spectrum runs from generic (unregistrable) through descriptive (difficult) to suggestive (registrable) to arbitrary (strong) to fanciful (strongest). "Apple" for computers is arbitrary. "Stripe" for payments is suggestive. "DataSync" for synchronization software is descriptive.
The strongest software trademarks are names that suggest something about the product without describing it directly. Think "Slack" (implies casual communication without saying "chat app"), "Notion" (implies ideas without saying "note-taking software"), "Figma" (doesn't describe anything about design tools).
3. Skipping the Clearance Search
Filing without searching is gambling $250-$350 that nobody else is using a similar name in your space. The money is the least of it. If your application gets refused for likelihood of confusion with an existing mark, you've lost 6+ months and still need to either rebrand or fight.
A basic search takes 30 minutes. A thorough clearance search takes a few hours. Either is cheaper than a rebrand.
What Happens After Registration
Registration is the beginning, not the end. Three things to know.
Maintenance filings. Between years 5 and 6 after registration, you must file a Section 8 Declaration of Continued Use (proving you're still using the mark). Between years 9 and 10, you file for renewal. Miss these deadlines and your registration is cancelled. Set calendar reminders now.
Monitoring. A registration gives you rights, but enforcing those rights is your responsibility. The USPTO doesn't police infringement. You need to monitor for new filings that might conflict with your mark and take action during the opposition window if needed.
International protection. A US trademark only protects you in the US. If your software has users in Europe, you'll want to consider an EUTM filing (covers all EU member states) or use the Madrid Protocol to extend protection to specific countries. International filing is a separate process with its own costs, which is covered in detail in the SaaS founder's trademark guide.
The Bottom Line
Getting a trademark for software follows the same process as any other registration, with two software-specific wrinkles: picking the right class (9 vs 42 vs both) and avoiding descriptive names that the USPTO will refuse.
The filing itself is not complicated. The clearance search matters more than the filing. And the cost of getting it wrong, a forced rebrand, a legal fight, or a dead application, is always higher than the cost of getting it right.
If you've shipped software that people use by name, a trademark filing should be on your list. Not today's list. This quarter's list. Run a clearance search before you file. And consult a trademark attorney for guidance specific to your situation, especially if your product name is close to anything else in your space.