USPTO Trademark Class Finder (free 2026 tool)

What this tool does

USPTO trademark registration requires selecting Nice Classification classes. Tool identifies correct classes based on your business description.

SaaS typically Class 42; ecommerce Class 35; physical goods vary by product type.

Who needs it

Delaware LLC owners filing US trademark applications.

How it works

1. Describe your products and services.
2. Tool maps to USPTO Nice Classification classes.
3. Returns recommended classes with fee estimates.

Inputs

• Business description
• Product/service types

Output

Recommended USPTO classes with fee estimates.

What does the USPTO Trademark Class Finder actually compute?

The finder reads a plain description of what your Delaware LLC sells and maps it onto the Nice Classification system, the international taxonomy the USPTO uses to sort every trademark application into numbered classes. There are 45 classes in total. Classes 1 through 34 cover physical goods, and classes 35 through 45 cover services. The tool does not invent classes. It pattern-matches your wording against the kinds of goods and services each class is meant to hold, then returns the classes that fit along with a fee estimate based on how many you end up filing in. The output is a starting shortlist, not a legal opinion, and you should treat it as a way to narrow a 45-item list down to the two or three that genuinely describe your business.

Reading the result is straightforward once you know the structure. Each recommended class comes with a number, a short label, and the reason the tool matched it to your description. A software company that wrote "we run a subscription web app for scheduling" will usually see Class 42 surface, because Class 42 holds "software as a service" and the design and development of computer software. The fee estimate multiplies the per-class government filing fee by the number of classes you select, so a two-class filing costs twice what a one-class filing costs. The point of computing this up front is that class count is the single biggest driver of what a federal trademark application costs, and picking classes carelessly is how applicants either overpay or leave gaps in their protection.

How do I read the inputs and outputs correctly?

There are two inputs. The first is your business description, where you write what you do in ordinary language. The more concrete you are, the better the mapping. "We sell things" produces noise, while "we sell roasted coffee beans direct to consumers and also run a coffee subscription box" produces a clean match because each phrase points at a recognizable class. The second input is the product or service type, a structured nudge that tells the finder whether you are primarily a goods business, a services business, or both. Use both fields together. The structured type narrows the universe, and the free-text description refines which classes inside that universe apply.

The output is a list of recommended USPTO classes with fee estimates. Read it as a ranked suggestion, not a verdict. For each class you should ask three questions before you accept it:

• Does this class describe something I actually sell today, not something I might sell later?
• Is the matched goods or services language broad enough to cover my real offerings without overreaching?
• Will filing in this class meaningfully protect the part of my brand customers recognize?

If a recommended class fails any of those tests, drop it. A trademark application that claims goods or services you do not provide can be challenged and, in some cases, invalidated for fraud. The fee estimate updates with the classes you keep, so removing a class you do not need lowers your cost. The finder errs toward showing you candidates, and the editing down is your job.

Worked example: a SaaS company filing one class

Suppose your Delaware LLC runs a hosted invoicing app sold by monthly subscription. You type "cloud-based invoicing and accounting software delivered as a subscription" and select "software / digital service" as the type. The finder returns Class 42 as the primary match, because Class 42 is the home of software as a service and platform as a service. It explains the match by pointing at the words "cloud-based," "software," and "subscription." The fee estimate shows the cost of a single-class filing, since one class covers the whole offering. This is the common shape for a pure SaaS business, and filing one well-drafted Class 42 registration usually protects the product line.

Where SaaS founders go wrong is assuming software always means a goods class like Class 9. Class 9 covers downloadable software, the kind a user installs and keeps. If your product never leaves your servers and customers only access it through a browser or an API, Class 9 is the wrong fit and Class 42 is right. The distinction is delivery, not function. If you both sell a downloadable desktop client and run a hosted version, you may legitimately need both Class 9 and Class 42, and the finder will surface both. In that case the fee estimate doubles, because you are filing in two classes. Decide based on what you actually ship, and let the class count follow from that rather than guessing at a single label.

Worked example: an ecommerce store with physical goods

Now suppose your LLC runs an online store selling its own branded candles. You describe it as "online retail store services featuring scented candles that we manufacture and sell." The finder is likely to return two classes. Class 35 covers retail store services, including the operation of an online shop, advertising, and business administration. Class 4 covers candles and related goods. These protect different things. The Class 35 mark protects your store brand, the name customers see when they shop. The Class 4 mark protects the product brand, the name on the candle itself. If those are the same name, you may want both.

This is the classic ecommerce split, and reading it correctly saves money and prevents gaps. A founder who files only in Class 35 protects the storefront but not the product, so a competitor could in principle sell candles under a confusingly similar name as long as they did not copy the store. A founder who files only in the goods class protects the product but not the retail operation. The finder shows both so you can make a deliberate choice. If the brand lives mostly on the product, lead with the goods class. If it lives mostly on the shopping experience, lead with Class 35. Many small sellers file both, accepting the higher fee because the brand and the product share one name they cannot afford to lose.

How does the goods-versus-services split change your filing?

The first fork in trademark classification is whether you are protecting goods, services, or both. Goods are things a customer takes away: a bottle of supplement, a t-shirt, a piece of hardware. Services are activities you perform for customers: running a store, hosting software, giving advice, repairing equipment. The same brand can live in both worlds, and the finder treats each independently. A clothing brand that designs and sells its own shirts lands in Class 25 for the garments. The same brand, if it also runs branded retail outlets, may add Class 35 for the retail services. Neither class implies the other.

Getting this fork right matters because the USPTO examines each class on its own. You must show that you use, or intend to use, the mark in commerce for the goods or services in every class you claim. If you file in a services class but only ever sell a product, the services claim is vulnerable. Conversely, claiming only the goods class leaves your service activities unprotected. Use the finder to map both sides of your business honestly, then keep the classes that match what you genuinely do. A useful habit is to write two sentences, one starting "we make and sell" and one starting "we provide the service of," and feed each into the description. If the second sentence is empty, you are probably a pure goods business and should ignore the service classes the finder might otherwise suggest.

What do the trademark filing fees look like per class?

Federal trademark fees are charged per class, not per application. That single rule explains most of the cost surprises applicants run into. If you file one application covering three classes, you pay the per-class government fee three times. The finder's fee estimate reflects this by multiplying the count of classes you keep. Because fee schedules change, the tool shows an estimate rather than a fixed quote, and you should confirm the current per-class fee on the USPTO website before you submit. The structural point holds regardless of the exact dollar figure: every class you add is another full filing fee, and most of the cost lever is in your hands at the class-selection step.

This is why pruning the finder's output is financially meaningful. Suppose it suggests four classes but two of them describe offerings you only plan for next year. Filing all four today means paying four per-class fees for protection you cannot yet support with proof of use. The cheaper and safer path is to file the two classes you actively use and add the others later when those products launch. The finder helps you see the full set of relevant classes, but the decision of how many to file in, and when, belongs to your budget and your roadmap. Treat the estimate as a planning number that scales linearly with class count, and remember that trademark fees are entirely separate from your Delaware LLC's $110 formation fee and its $300 annual franchise tax due each June 1. None of those cross over.

Why is Class 9 different from Class 42 for software?

Software sits in a spot that confuses almost every first-time filer, so it is worth pinning down. Class 9 is a goods class. It covers downloadable and recorded software, the kind a user obtains as a file, installs, and runs locally, including mobile apps a user downloads from an app store. Class 42 is a services class. It covers software as a service, where the user never possesses the code and instead accesses functionality hosted on your servers. The finder decides between them by looking for delivery cues in your description: words like "download," "install," and "app" pull toward Class 9, while "hosted," "cloud," "subscription," and "access" pull toward Class 42.

Many modern products genuinely span both. A company might ship a downloadable mobile app and run a web dashboard hosted in the cloud. In that case both classes are correct, and the finder will return both with a two-class fee estimate. The mistake to avoid is reflexively picking Class 9 because the word "software" feels like a product. If customers only ever reach your software through a browser or an API and never download anything, Class 9 adds cost without adding protection that matches your real use. Read the matched language the finder shows for each class and confirm it describes how your software actually reaches users. The delivery model, not the marketing label, decides the class.

What are the common mistakes when picking classes?

The errors cluster into a few repeatable patterns, and knowing them lets you sanity-check the finder's output before you file. Each one either wastes money or weakens the registration:

• Claiming classes for products you plan but do not yet sell, which exposes the application to challenge for lack of bona fide use.
• Picking a goods class for a hosted service, or a service class for a downloadable product, because the delivery model was misread.
• Filing in only one class when the brand name is used for both a store and the product it sells, leaving half the brand unprotected.
• Writing a description so broad the examiner cannot tell what you do, which delays the application with office actions.
• Writing a description so narrow it misses adjacent offerings, forcing a second filing later.

The cure for most of these is specificity in the description you feed the tool and honesty in the classes you keep. Describe what you sell today, in concrete terms, and let the finder map it. When the output lists a class, open the matched language and ask whether it describes a real, current offering. If yes, keep it. If it describes an aspiration, set it aside for a future filing. Over-claiming feels like cheap insurance but it is the opposite, because a registration built on goods or services you do not actually provide is weaker than a narrow one built entirely on real use. The finder gives you the candidates so you can apply this judgment deliberately rather than picking classes by gut feel.

How precise should my goods and services description be?

Precision in the description does double duty. It improves the finder's class match, and it also previews the identification of goods and services you will eventually write on the application itself, which the examiner reads closely. A vague entry like "business services" matches almost nothing useful and, on a real application, would draw an objection. A precise entry like "providing temporary use of online non-downloadable software for managing customer appointments" matches Class 42 cleanly and reads like acceptable identification language. The habit of writing precisely here pays off twice.

Aim for descriptions that name the thing and its delivery. For goods, name the product and what it is: "scented candles made of soy wax" rather than "home goods." For services, name the activity and who it serves: "online retail store services featuring kitchenware" rather than "sales." If your business does several distinct things, write a short clause for each and feed them together, because the finder can return multiple classes from one rich description. The goal is not length but coverage of the distinct activities that earn revenue. When you later draft the application, you can reuse these clauses, tightening them against the USPTO's acceptable identification manual. Specific input produces a class list you can trust, and a class list you can trust is what keeps the filing cheap and clean.

What about international and multi-class filings?

Because the Nice Classification is international, the class numbers the finder returns travel well. The class that covers your software in the United States is the same numbered class that covers it in most other Nice member countries. That matters if your Delaware LLC plans to register the same mark abroad, whether through national filings or the Madrid Protocol, which lets you extend a base application to multiple countries. The classes you settle on now become the backbone of any later international strategy, so it is worth getting them right before you expand. The finder does not file abroad, but the class numbers it gives you are the same currency every Nice country uses.

Multi-class filing is the other piece. In the United States you can file one application covering several classes, paying the per-class fee for each. This is convenient but it does not discount the fees, and it ties the classes together administratively. Some applicants prefer separate single-class applications so that a problem in one class, such as an office action or an opposition, does not stall the others. The finder helps you decide by showing the full class set and the total estimated fee, after which you choose the filing structure. If protecting one core class quickly matters more than protecting everything at once, file that class alone and add the rest later. If you want a single docket to manage, file multi-class. Either way, the per-class fee is the same, so the choice is about timing and risk rather than cost.

What do I do with the result once I have it?

The finder's output is the start of a filing workflow, not the end. The next step is a clearance search: before you spend on registration, check whether anyone already holds a confusingly similar mark in the classes you picked. A name that is free in Class 25 might be taken in Class 35, so search within each class on your shortlist. Many applicants pair the class finder with a name-availability check so they enter the trademark process knowing both which classes they need and whether the mark is open in them. Skipping the search is how applicants pay filing fees only to receive a refusal based on a prior registration.

After clearance, you draft the application using the classes and the goods or services language you refined here, file through the USPTO's electronic system, and pay the per-class fees. Keep the finder's shortlist as a record of why you chose each class, because if an examiner questions a classification you will want to explain your reasoning. Remember that trademark work is wholly separate from your entity's compliance calendar: the federal EIN you request on Form SS-4, which arrives in roughly 8 to 10 business days for free, the franchise tax due each June 1, and any tax filings such as Form 5472 with Form 1120 all run on their own tracks and carry their own penalties, like the $25,000 penalty for a missed 5472. The class finder touches none of that. Its job is narrow and useful: turn a description of your business into the right numbered classes so the trademark you file protects what you actually sell.