What Espacenet Is and Why It Belongs in Your Search

Espacenet is the free patent database published by the European Patent Office, and despite the European name it is one of the best places for a US inventor to start checking whether an idea is new. It indexes well over a hundred million patent documents from roughly a hundred patent offices — US grants and published applications included — and adds three things a single-country search cannot give you: machine translation of Chinese, Japanese, Korean and German documents into English, a family view that groups every national version of one invention, and classification browsing that finds documents your keywords never would. There is no account to create and no charge per search.

One framing note before the mechanics. Espacenet is a finding tool, not an opinion. It will not tell you whether a US patent is currently enforceable, how broadly a claim reads, or whether your product infringes. Projects House is an engineering firm, not a law firm, and this article is educational only — conclusions about validity or infringement belong with a registered patent attorney.

Espacenet or the USPTO's Own Search?

Both, in that order of convenience. Patent Public Search at the USPTO is the authoritative full-text source for US documents and the place to confirm anything about a US file. Espacenet is the better net: it surfaces the Chinese utility model or the Japanese application describing your idea a decade ago, which is prior art against you no matter where it was filed. Our comparison of free patent search tools lays out how the major databases divide the work. A serious novelty check uses at least two of them.

Step 1: Smart Search, Not a Single Word

The Espacenet search bar accepts field codes, which is what separates a five-minute search from a useful one. The codes worth memorizing:

  • ti= title only — precise but misses a great deal, because patent titles are deliberately vague.
  • ta= title and abstract — the best default for a first pass.
  • ctxt= full text, including description and claims — high recall, high noise.
  • cl= claims only — useful when you want documents that actually claim the feature rather than mention it.
  • pa= applicant and in= inventor — for tracking a specific company or engineer.
  • cpc= and ipc= — classification codes, covered below.
  • pn= publication number, when you already have a document in hand.

Combine them with AND, OR and NOT, use quotation marks for exact phrases, and use truncation aggressively: an asterisk stands for any number of characters, so fold* catches folding, foldable and folded. A query like ta=(collapsible OR foldable OR "folding frame") AND ta=(wheelchair OR walker) is the shape you are aiming for — synonym groups combined with AND, not one clever phrase.

Search in English even if your notes are not. Start broad and narrow deliberately; a thousand hits you filter down beats forty hits that missed the blocking document. And search the way a patent attorney writes, not the way a customer talks — that translation is the real skill, and we cover it in detail in our guide to choosing patent search keywords.

Step 2: Switch From Words to Classification

Every patent document is assigned CPC and IPC codes by an examiner who read it, which makes classification immune to vocabulary problems. The practical route is backward: run keyword searches, open the four or five closest hits, and note the classification codes on each front page. Codes that repeat across your best hits are your shelf. Search cpc= against those codes, optionally intersected with one keyword group, and you will see documents no phrasing would have surfaced. Our article on patent classification search explains how to read the code structure and use the official scheme definitions.

Step 3: Use Families, Legal Status and Citations

Three Espacenet tabs do most of the heavy lifting once you have a relevant document open:

  • Patent family — every publication worldwide covering the same invention. If a family has US, European and Chinese members, the applicant is serious; if it never left one country, your market may be open even where the idea is not new.
  • Legal status — the INPADOC events feed, which shows lapses, withdrawals and national entries. Read it as a lead, then verify in the national register. Our guide to checking whether a patent is still in force covers the US verification steps.
  • Cited documents and citing documents — the citation web. Documents the examiner cited against your target are the closest prior art in that field; documents that later cite it are the newer players. Following citations two hops in each direction maps a technology area faster than any keyword list.

Step 4: Read the Hits Properly and Log Everything

A hit is not a problem until you have read its claims. Drawings mislead constantly — a figure can look exactly like your product while the claims cover something narrower or entirely different. Work through how to read a patent before you judge anything you find, and use the description as a vocabulary mine for the next search round.

Keep a simple spreadsheet: query string, database, number of hits, and the publication numbers worth a second look with a one-line note each. Without it you will repeat searches, forget which synonym groups you already tried, and pay an attorney to redo work you already did. With it, you arrive at a professional prior art search with a documented starting point, which makes that work faster and cheaper.

Where a Free Search Stops

An Espacenet session usually ends in one of three states: nothing close was found and filing is worth discussing; a document sits squarely in your path and the design needs to move; or the field is crowded and differentiation is the real problem. All three are useful, and none of them is a legal conclusion. Free databases have real limits — non-patent prior art such as product manuals, catalogs and academic papers is outside them entirely, and unpublished applications stay invisible for about eighteen months after filing.

Search First, Then Engineer

The cheapest hour in product development is the one spent searching before anything is designed. We run this kind of search at the front of engineering projects because it shapes the design: a blocking document found early is a design constraint, and the same document found after tooling is a lost budget. If you want engineering help interpreting what you found and designing around it, send us your idea through the contact form and we will tell you what we see.