Selected startups can get 50% off their first year with Patentext, up to $3,000. Apply to the Startup Program →

Patent drawings: requirements, examples & FAQs

Learn when patent drawings are required, what they should include, and how to meet the USPTO’s drawing requirements.

You may already have sketches, CAD models, or system diagrams that explain your invention to your team. But when it’s time to prepare a patent application, it’s not always clear whether those materials are enough. Can you submit the drawings you already have? Which details need to appear? And do you need someone to prepare a new set?

Patent drawings help readers understand details that are hard to explain in words, from how mechanical parts fit together to how information moves through a software system. This guide covers the decisions on what to show, with examples and practical advice on how to meet the USPTO’s drawing requirements.

Note: This guide focuses on U.S. applications for inventions such as devices, systems, and processes. Design patents have different drawing considerations.

Are patent drawings required?

Yes, when drawings are necessary to understand the subject matter being patented. For a mechanical assembly, that might mean showing how parts fit together. For a software system, a block diagram or flowchart may explain relationships that are hard to follow in prose.

The USPTO’s non-provisional application guide also requires drawings to show the features specified in the claims. Work through the figures alongside the description and claims rather than treating them as illustrations to add at the end.

What are the USPTO patent drawing requirements?

Drawings need to communicate clearly and reproduce reliably. This table summarizes the requirements teams most often need to check.

CheckRequirement for non-provisional drawings
Sheet sizeA4 (21.0 × 29.7 cm) or U.S. letter (21.6 × 27.9 cm). Use the same size throughout.
Minimum marginsTop and left: 2.5 cm. Right: 1.5 cm. Bottom: 1.0 cm.
Lines and shadingUse clean, dark, reproducible lines. Appropriate shading can explain shape, but must preserve legibility.
CharactersKeep numbers, letters, and reference characters legible and at least 0.32 cm high.
WordingUse only the descriptive wording needed to understand the figure.
ScaleShow the mechanism without crowding after reduction to two-thirds. Omit actual-size or scale-ratio labels.

When discussing these requirements, you may hear drawings described as ‘formal’ or ‘informal.’ USPTO guidance uses acceptable and unacceptable. A rough sketch is useful technical input, but that label alone tells you nothing about whether it is suitable for filing.

What drawings should a provisional application include?

Include the drawings needed to understand the invention when you file. A provisional can receive a filing date without drawings, but receiving a date does not establish that the disclosure adequately supports a later claim.

Start with the relationships that would be difficult to reconstruct from the text alone:

  • For hardware, show the relevant parts, their arrangement, and how they interact.
  • For software, show the relevant system connections, processing steps, and decision points.
  • Include important alternatives where a single diagram would otherwise leave the technical explanation incomplete.

A missing mechanism is not a formatting problem you can safely postpone. Necessary drawings cannot simply be supplied later as new matter while keeping the original filing date.

How many figures and views do we need?

Use as many figures and views as you need to explain the invention clearly. Once you’ve identified the components or steps that need to appear, consider whether a reader can understand them from the views you’ve chosen. An external view of a device might show its overall shape while hiding an important internal mechanism. Adding a section view could explain more than several additional views of the outside.

Choose each view for the question it answers:

  • An overview shows the system or assembly; a detail view shows a feature that would otherwise be too small.
  • A section reveals internal structure; an exploded view can clarify how parts fit together.
  • A block diagram shows relationships between components; a flowchart shows steps and decisions.

Keep the views consistent. A component should not change shape, position, or identity between views unless you are deliberately showing and explaining a different implementation or operating state.

How should reference numerals match the written description?

Use the same reference character for the same part across views, and make sure the description and drawings account for the characters used. You do not need a fresh numeral every time you mention a feature.

Three numbering systems do different jobs:

  • Sheet numbers identify pages, such as 1/3 for the first of three drawing sheets.
  • Figure numbers identify views, such as FIG. 1 and FIG. 2. They are independent of sheet numbers; an application with only one view uses no figure number or FIG. label.
  • Reference numerals identify features within a view, such as sensor 100 and controller 110.

Treat a numeral as a stable name. If 110 means the controller in one figure, do not reuse it for the cloud service in another. Label repeated features where needed for clarity without turning the page into a thicket of leader lines.

Can we use sketches, CAD exports, photographs, or color?

Sketched ideas and CAD exports are useful starting materials. Whether the resulting figures are acceptable depends on their content and presentation, not the software that produced them. Check the exported sheets rather than assuming the source file settles the question.

For photographs and color, the rules are more specific:

  • Black-and-white photographs may be accepted when they are the only practicable way to illustrate the claimed invention, such as certain biological specimens. They do not universally require a petition or petition fee.
  • Color drawings in a U.S. non-provisional application require a granted petition explaining why color is necessary, the petition fee, the required specification statement, and the appropriate drawing sets. Electronic submission requires one set; non-electronic submission requires three. Color photographs must satisfy the applicable photograph and color conditions too.

Design applications have different color provisions, and PCT international applications have their own restrictions. Ask your practitioner to check the filing route before relying on a color image. For ordinary non-provisional figures, start with clear black-and-white drawings.

What figures are useful for software and system inventions?

Use figures that explain where the work happens and how information moves. A box marked “AI engine” does little on its own. The useful detail is what enters it, what processing occurs, and what comes out.

Depending on the invention, that could mean:

  • An architecture diagram showing devices, services, storage, and their connections.
  • A flowchart showing processing order, branches, and what happens when a condition is not met.
  • A data-flow or sequence diagram showing which component sends which information, and when.

Here’s a simplified, hypothetical example. It illustrates coordination between a figure and its description, not a complete filing template.

Illustrative data path showing sensor 100 sending readings to local controller 110, which sends filtered data to cloud service 120
Illustrative system diagram: readings pass through local controller 110 before reaching cloud service 120.

Matching description: Sensor 100 sends readings to local controller 110. Local controller 110 filters the readings and transmits the filtered data to cloud service 120 for storage.

Now change the description to say that sensor 100 sends readings directly to cloud service 120. That is a different data path from the one shown. Does the controller filter the readings first, or does the sensor bypass it? Resolve that with the engineering team. If both paths are intended alternatives, explain and depict them as alternatives.

Can we create patent drawings ourselves or use AI?

Yes. There is no blanket requirement to hire an illustrator, and the USPTO’s AI guidance does not impose a blanket ban on AI-assisted drawings.

Whether you opt for CAD software or generative image tools, make sure:

  • Components and connections match the actual invention.
  • Labels and reference numerals stay consistent across figures and text.
  • Flowcharts preserve the intended sequence, branches, and decision logic.
  • Different views depict the same structure or clearly identified alternatives.
  • Generated details have not introduced features the invention does not contain.

For a complete list of AI patent tools, check out this guide.

What happens if drawings are incomplete or inconsistent?

The answer depends on what is wrong. A faint line and a missing technical relationship are different problems, even if both first show up as a comment on a figure.

Presentation problems, such as poor reproduction or incorrect sheet layout, may be addressed with corrected drawings. Follow the actual USPTO notice and response period; there is no single notice or deadline that applies to every drawing issue.

Missing disclosure is more serious. A correction cannot introduce new matter, and an omitted mechanism can leave the application without support for the protection you wanted. Check the original text and drawings before assuming a new figure can fix it.

For an inconsistency, first establish which version is technically correct. Then have your practitioner assess what the filed disclosure supports and how to address the discrepancy.

How much do patent drawings cost?

The cost of a patent drawing depends on the complexity of the invention and the number of views required, but most professional patent drawings range from $50 to $150 per drawing.

Here’s a breakdown of common price factors:

  • Simple line drawings (e.g., a basic mechanical device): $50–$75.
  • Moderate complexity (e.g., electrical schematics or layered assemblies): $75–$100.
  • Highly detailed or intricate drawings (e.g., medical devices, exploded views): $100–$150 or more.

Costs can also increase if the drawings require:

  • Multiple revisions to meet USPTO standards.
  • Color or shading (if approved as necessary).
  • Specialist software or expertise, such as for 3D models or chemical diagrams.

What should our engineering team provide?

You do not need to arrive with polished patent figures. Bring the materials that let someone ask the right technical questions:

  • Existing sketches, architecture diagrams, or CAD exports, with an explanation of the components and their interactions.
  • Important operating steps and alternative implementations, including the technical details that distinguish the invention from existing approaches.
  • A named technical contact who can answer clarification questions and confirm revisions.

Our invention disclosure checklist helps organize this material. If you’re planning an early filing, also review the provisional filing mistakes that can leave technical gaps.

Get your application and drawings prepared with Patentext

If you have sketches or technical diagrams but aren’t sure how to turn them into patent drawings, those materials can be your starting point. Patentext’s guided invention disclosure process helps you explain the components, connections, and operating steps behind your invention. Patentext Services’ USPTO-registered patent agents then use that information to prepare your application, including the required drawings—which are included in both our provisional and non-provisional application services.

Explore patent application services.

Disclaimer: This article is for informational purposes only and does not constitute legal advice. Patent laws are complex and vary by jurisdiction. For personalized guidance, consult a qualified patent attorney or registered patent agent.

Alexander Flake

Alexander Flake

CEO & co-founder, Patentext · Registered patent agent

Alex is the co-founder and CEO of Patentext. He has spent more than a decade preparing and prosecuting patent applications for startups, growth-stage companies, and technology companies including Uber and Dropbox.

Connect on LinkedIn

Keep the invention context working.

See how Patentext connects invention capture, evaluation, and professional patent services.

Explore the platform