How to Trademark a Software Name: Class 9, Class 42, Specimens, and Enforcement

How trademarks work for software and SaaS products: clearing the name, choosing one the USPTO will register, picking the right trademark class, timing the filing to the launch, proving use with a specimen, and defending the mark afterward.

Yes, a software, app, or SaaS product name can be registered as a trademark, and usually should be. Trademark protection in the United States comes from using the mark in commerce, and federal trademark registration adds prima facie evidence of validity and ownership, nationwide constructive notice, the ® symbol, and the practical currency for app-store and domain disputes (15 U.S.C. §§ 1057, 1072, 1115). So the short answer to how to trademark a software name is to clear it, file the right application in the right class, and prove use with the right specimen.

Three things make software trademarks different from a restaurant name: the class question (is the product a downloadable good, an online service, or both), the specimen question (how do you prove use of a mark for something that lives on a server), and the naming problem that tech names skew descriptive. The application form itself is easy, and the decisions behind it are where registrations are won or refused. For how trademarks fit with copyright and trade secrets, start with the Protection of Software page.

What a trademark or service mark protects for a software company

A trademark identifies the source of goods, and a service mark identifies the source of services. Product names, company names used as brands, logos, and taglines all qualify; the code itself is protected by copyright and trade secret, the other layers of intellectual property, and not by trademark law. Registering an LLC, buying a domain, or claiming an app-store name creates no trademark rights by itself, though a domain can function as a mark when it is used as a brand.

The line that runs through the rest of this page is the goods and services line. Downloadable software distributed for the buyer’s installation is a good, while software hosted on your server and used through remote access is a service, and that one distinction decides the class, the specimen, and the use-in-commerce analysis. Use ™ on any mark you claim and ® only after federal registration issues.

Step 1: Clear the name before you build the brand identity around it

A trademark strategy starts with clearance, which asks whether the name is likely to be confused with an existing mark, weighing the similarity of the marks, the relatedness of the goods and services, the trade channels, and the strength of the prior mark. In an infringement suit in North Carolina, the Fourth Circuit’s factors apply, with actual confusion the most important; in RXD Media v. IP Application Development, the “iPad” case, survey confusion of 27 percent supported summary judgment for Apple.

Two points surprise software companies. Class 9 and Class 42 are not a safe harbor from each other, because relatedness turns on the field the software serves rather than the delivery format; “online non-downloadable software” for market research was closely enough related to registered “computer software for database management” to support confusion. And geography no longer helps: the Fourth Circuit held in Westmont Living v. Retirement Unlimited that the old geographic-market rule has little force where both parties market nationally online, so being in a different state is no defense for a SaaS company.

A real trademark search goes beyond the USPTO register to state registrations, common-law users, domains, app-store listings, social handles, and package names for developer tools, and it verifies every hit on the USPTO’s own records instead of trusting the vendor report. The knockout search is fast and cheap; the judgment about whether a hit is a real problem, and whether to file anyway with a narrower identification, is the work.

Step 2: Choose a name the USPTO can register

Fanciful and arbitrary names are strongest, suggestive names are registrable, merely descriptive names are refused unless they acquire distinctiveness, and generic terms can never be registered. An ordinary word can be arbitrary and strong; the Federal Circuit’s paradigm is “APPLE for computers.” Tech buzzwords are usually descriptive or weak, since a term is merely descriptive if it immediately conveys a quality, feature, or function of the goods; DEALERDASHBOARD was descriptive of dealer information services because “a dealer dashboard is a dashboard for dealers.” Expect “AI,” “cloud,” “hub,” “analytics,” or “pay” plus the function to draw a refusal or a disclaimer.

Adding “.com” does not rescue a descriptive name; the Supreme Court held in USPTO v. Booking.com that there is no per se rule against generic-plus-.com marks, but even a registrable one is weak and narrow, and PATENTS.COM was descriptive of patent-tracking software. A descriptive word inside a composite mark gets disclaimed, and the more descriptive the name, the more proof of acquired distinctiveness it needs. How you describe the goods can also invite a refusal of the mark; on a tax-compliance SaaS application, leaving “tax” out of the goods description avoided handing the examiner a descriptiveness argument. A suggestive name that clears beats a descriptive one the marketing team loves.

Step 3: Trademark class: Class 9, Class 42, or Class 35 for software services?

Software companies register trademarks in three classes. Downloadable computer software, computer programs, and mobile apps are goods in Class 9, alongside computer hardware. Software as a service, hosting, and other non-downloadable software are services in Class 42, whose official heading also covers scientific and technological services, research services, and the design and development of computer hardware and software, which is why software development shops file there too. Online retail, marketplaces, and business services delivered through software belong in Class 35, just as a physical store would. The same product can be a good when downloaded and a service when hosted, so map every delivery mode to its class before filing. The client question that comes up most often is “if the product is SaaS, is it downloadable?” Hosted, browser-accessed software is Class 42, an installed client or mobile app is Class 9, and many products are both.

The USPTO requires software identifications to state the function and, where applicable, the field of use; “software” alone is indefinite, and an identification can be narrowed after filing but never broadened. The ID Manual lead-ins that work are “Downloadable computer software for {function}” and “Providing on-line non-downloadable software for {function}.” For a platform, one identification per distinct revenue stream is the rule: on a branded-merchandise platform, the ordering and fulfillment services went in Class 35 and the operating software went in Class 42.

Fees are per class. The USPTO’s base filing fee is currently $350 per class, with a $200 surcharge per class if the identification is not from the ID Manual, so a compliant description saves money as well as examination time; fees change, so check the USPTO’s current schedule. Add classes only where there is real use or intent, because each one has to be supported by its own specimen later.

Step 4: Use-based or intent-to-use: timing the trademark application to the launch

A use-based application requires current use in commerce, dates of first use, a specimen, and a sworn statement that the mark is in use. An intent-to-use application requires only a bona fide intention to use the mark, and it cannot register until a statement of use is filed after allowance. The prize for filing early is priority: contingent on registration, the filing date counts as constructive nationwide use, ahead of everyone but a prior user (15 U.S.C. § 1057(c)). That is why intent-to-use is the standard pre-launch move, filed at the moment the name is chosen and before the domain purchase, the app-store listing, and the launch post make it public.

The signature deserves a word, because the form makes it look routine: the signer swears that the mark is in use, or that the intent is bona fide, and that false statements are punishable, so filing use-based before there is real use is one of the ways registrations get cancelled.

Step 5: The specimen: proving use for downloadable goods or services delivered online

For downloadable software in Class 9, the specimen must show the mark on the goods or on a display of a point-of-sale nature, which for software means a webpage showing the mark together with a way to download or purchase, or the software’s own screens; advertising alone is not enough. A SaaS specimen in Class 42 must instead show the mark used in selling or advertising the services, with a direct association between the mark and the services, such as a webpage or in-app screen that describes the services offered under the mark. Web site specimens need the URL and the date, and mock-ups are barred by rule.

Submitting a specimen that does not show real use is a material misrepresentation that supports cancellation; in OpenAI, Inc. v. Open A.I., Inc., a substitute specimen showing a product that was not yet available on the application date cost the registrant its registration. One example from practice shows the fix when a specimen is refused for not showing that the software is downloadable: a webpage showing the mark with the software, followed by the email the company sends users with download instructions from the same domain, documents the delivery flow the identification describes. Specimens are a launch-planning item, and if the only public use is a couple of social media posts, the choice is intent-to-use or waiting for real marketing pages.

Step 6: From filing to federal registration: the application process and office actions

The application asks for the owner, the mark (as a standard character mark or a stylized drawing), the goods or services by class, the basis, dates of first use, the specimen, and the declaration. Examination takes months to a first action, and an office action may raise likelihood of confusion, descriptiveness, identification, or specimen issues; then comes publication for opposition and either registration or, for intent-to-use filings, a notice of allowance followed by the statement of use. Office actions are where most self-filed software applications die; the identification and specimen fixes above are routine for a trademark attorney, which is why the trademark registration process is usually handled on a flat fee for the application and hourly for responses.

Domain names and app-store names

App-store disputes run through each platform’s own process under a developer agreement you cannot negotiate, and a federal registration is the evidence platforms expect for a name complaint or takedown. For domains, the Anticybersquatting Consumer Protection Act reaches anyone who registers or uses a confusingly similar domain with a bad-faith intent to profit, and the UDRP offers a faster administrative route limited to transfer or cancellation. Fourth Circuit authority here is unusually deep, because the .com registry sits in the Eastern District of Virginia and the statute allows an in rem action against the domain itself; the domain name dispute case study shows how one of these plays out.

After the registration process: licensing, maintenance, and enforcement

A licensee’s use counts as yours only if you control the nature and quality of what is sold under the mark (15 U.S.C. § 1055); a license with no quality control, a “naked license,” can cause the mark to be deemed abandoned. The trademark license section of a reseller or white-label agreement, where a partner trades on your brand recognition, is the one most often missing, and a mark is assignable only with the goodwill of the business, so acquisition documents should recite it.

A registration lives on maintenance filings: a declaration of continued use between the fifth and sixth years and again every ten years, plus a renewal every ten years (15 U.S.C. §§ 1058, 1059). Missing a window cancels the registration, and post-registration audits now delete goods and services you cannot prove use for, so do not pad a software identification with functions the product does not perform. For SaaS, “use” means a live, operating service, so keep dated evidence that customers were using it.

Enforcement runs from monitoring and demand letters to Lanham Act claims, and in North Carolina a well-pleaded infringement claim also states a claim under the unfair and deceptive trade practices statute, with treble damages. Fee-shifting runs both ways, and the Fourth Circuit awards fees to prevailing defendants in exceptional cases as readily as to plaintiffs, as the trademark defense case study shows.

Common mistakes, and what to bring to a trademark attorney

• Launching before clearance, then discovering the name is taken or descriptive.
• Filing in Class 9 only for a product delivered as SaaS, or vice versa, and failing on the specimen.
• Submitting a marketing page as a specimen with no download or purchase mechanism.
• Registering the mark in the founder’s name instead of the operating company’s.

This page explains how software trademarks generally work; whether a particular name can be registered or enforced depends on the mark, the goods and services, and the existing register, and it is not legal advice (the site’s Disclaimer page has the details). When you are ready to talk to counsel, bring the names and logo files, how the product is delivered, what the software does in plain words, dates and evidence of first use, the owner entity, and any similar names or letters you already know about. Clearing and registering a name before launch is worth a conversation with experienced software counsel, because it heads off the forced rebrand that costs ten times as much after the fact.

Frequently asked questions