> For the complete documentation index, see [llms.txt](https://docs.protoboard.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.protoboard.xyz/help/faq.md).
# FAQ
Frequently asked questions about Protoboard, covering what it does, how to use it, and what to expect.
Answers to the questions we hear most often. Can't find what you're looking for? Check the [Troubleshooting](/help/troubleshooting.md) page for specific issues, or reach out through the in-app feedback button.
***
What is Protoboard?
Protoboard is a hardware validation platform. You design systems by placing parts on a canvas, connecting them with harnesses, and running a Design Rule Check (DRC) to verify that everything is compatible before you buy a single component.
Think of it as a spell checker for hardware designs. It catches voltage mismatches, protocol incompatibilities, role conflicts, and other issues that would otherwise surface only after you've soldered things together.
Protoboard supports electrical, mechanical, pneumatic, and other engineering domains. For more detail, see the [Quickstart](/start-here/quickstart-10-minutes.md).
Is Protoboard free?
Protoboard has a **Free tier** and a **Pro tier**.
* **Free:** Full access to the canvas, parts library, DRC, and BOM, plus a daily allowance of ProtoBot energy for AI assistance.
* **Pro:** Everything in Free, plus a larger daily energy allowance, priority support, and access to advanced features as they ship.
You can do meaningful work on the Free tier. Pro is worth it if you use ProtoBot heavily. Current allowances are shown in the app, since they change as the product evolves.
What parts are available in the library?
The parts library is powered by **ProtoPart**, an open-source parts repository. It includes hundreds of real-world components across multiple categories:
* **Microcontrollers:** Arduino Uno Rev3, Arduino Nano, Arduino Mega 2560, Raspberry Pi 5, Teensy 4.1, Seeed XIAO ESP32C3
* **Sensors:** BME280, HCSR04, VL53L0X, MLX90614, LSM6DS3TR-C, SCD40, MAX30102
* **Motor controllers:** L298N, REV SPARK MAX, TB6600, TI DRV8871, Adafruit Motor Shield V2
* **Motors and servos:** Tower Pro SG90, REV NEO Brushless, StepperOnline 17HS08
* **Power:** Ovonic 4S LiPo, MCP16251T regulator, MCP73831T charger, REV PDH
* **Pneumatic:** SMC KQ2H fitting, FRC Compressor, Pneumatic Piston, Tailonz Solenoid Valve
The library is growing continuously. If a part isn't available, you can create a **blank part** with custom interfaces and resources. See [Parts: Add / Edit / Custom](/user-guide/parts-add-edit-custom.md).
Can I add custom parts?
Yes. You can create **blank parts** from scratch in the Parts Bin. A blank part needs at minimum:
1. A name
2. At least one domain (Electrical, Mechanical, etc.)
3. At least one interface (the connection points other parts can link to)
4. Resources (the internal functions the part provides)
Custom parts work exactly like library parts; they participate in harnesses, DRC validation, and the BOM. For a hands-on walkthrough, see the [Breadboard from Blank Parts](/tutorials-and-examples/breadboard-from-blank-parts.md) tutorial.
What does the DRC actually check?
The Design Rule Check (DRC) validates your board across several dimensions:
* **Protocol compatibility:** Both sides of a connection must use the same protocol (I2C to I2C, SPI to SPI, etc.)
* **Role matching:** Roles must be complementary (master to slave, supply to return, driver to motor, output to input)
* **Voltage domain overlap:** The output voltage range must fall within the input's acceptable range
* **Resource allocation:** Physical pins must be assigned to logical functions
* **Resource availability:** You can't allocate the same pin to two different functions
* **Bus capacity:** I2C buses have device limits, power rails have current limits
The DRC reports results as CONFIGURED (green), PARTIALLY\_CONFIGURED (amber), NOT\_CONFIGURED (red), or INCOMPATIBLE (red). See [Validation (DRC)](/user-guide/validation-drc.md) for the full details.
What is ProtoBot?
ProtoBot is Protoboard's built-in AI assistant. You'll find it in the left sidebar (bot icon). It has access to over 100 specialized tools and can:
* Search the parts library and place parts on the canvas
* Create harnesses and auto-link compatible interfaces
* Run DRC and help interpret the results
* Allocate resources (pins) and fix configuration issues
* Manage the BOM
* Do web research to find datasheets and application notes
ProtoBot uses an energy-based pricing system (see the next question). For more, see [ProtoBot Overview](/protobot/overview.md).
How does the energy (Wh) system work?
ProtoBot usage is measured in **watt-hours (Wh)**. Different AI models consume energy at different rates; more capable models use more energy per interaction.
Your allowance refreshes every 24 hours from your first message. You can see your current balance in the ProtoBot panel. To conserve energy, stay on the default model for simple tasks (search, placement) and save heavier models for complex reasoning (DRC diagnosis, design optimization).
For detailed guidance, see [Usage, Energy, and Privacy](/protobot/usage-and-energy.md).
Can I share my designs with others?
Yes. Use the **Share** button in the top bar to generate a share link for your board. Recipients can view the design in their browser.
{% hint style="info" %}
**Current limitation:** Real-time collaboration (multiple users editing the same board simultaneously) is not supported yet. Sharing is view-only or turn-based; one user edits at a time. See [Known Limitations](/help/known-limitations.md) for details.
{% endhint %}
What export formats are available?
The BOM panel supports exporting to:
* **CSV**: for importing into spreadsheets, purchasing systems, or inventory tools
* **PDF**: for documentation, project proposals, or printing
EDA format exports (KiCad, Eagle, Altium) are not yet available but are on the roadmap. See [Known Limitations](/help/known-limitations.md) and [BOM + Export](/user-guide/bom-and-export.md).
Can I use Protoboard offline?
No. Protoboard is a web application that requires an internet connection. Your board data syncs to the cloud, and features like ProtoBot, parts library search, and BOM pricing require server access.
If you lose connectivity while editing, Protoboard has autosave drafts that help prevent data loss. When you reconnect, your latest changes should sync automatically.
What browsers are supported?
Protoboard works best in modern Chromium-based browsers:
* **Google Chrome** (recommended)
* **Microsoft Edge**
* **Brave**
Firefox and Safari are generally supported but may have minor rendering differences on the canvas. For the best experience, use the latest version of Chrome.
How do I report a bug?
Use the **feedback button** in the app (usually in the bottom-left corner or accessible from the help menu). Include:
1. What you were trying to do
2. What happened instead
3. Steps to reproduce the issue
4. Your browser and operating system
Screenshots and screen recordings are extremely helpful. If the issue involves a specific board, mention the board name so the team can investigate.
Is my design data private?
Yes. Your boards are private to your account by default. No one can see your designs unless you explicitly share them using the Share button.
Protoboard does not use your design data to train AI models. ProtoBot interactions are processed by third-party AI providers (the model you select), but your board data is transmitted securely and not retained for training purposes.
For complete details, see the [Privacy Policy](/legal/privacy-policy.md).
What's the difference between Free and Pro?
### Free
* Full canvas, parts library, DRC, BOM
* A daily allowance of ProtoBot energy
* Community support
* All export formats (CSV, PDF)
### Pro
* Everything in Free
* A larger daily ProtoBot energy allowance
* Priority support
* Early access to new features
Both tiers have full access to the core workflow. The primary difference is ProtoBot energy: if you rely on AI assistance for complex boards, Pro gives you substantially more budget. Current allowances are shown in the app.
Does Protoboard replace KiCad, Eagle, or Altium?
No. Protoboard is a **hardware validation and planning** tool, not a PCB layout or schematic capture tool. It sits earlier in the design process: you use Protoboard to verify that your parts are compatible and your system architecture makes sense, before moving to a traditional EDA tool for PCB design.
Think of it as the step between "I have an idea" and "I'm laying out a PCB." Protoboard helps you catch expensive mistakes (wrong voltage, incompatible protocols, missing connections) before you invest time in detailed schematic and layout work.
***
## Still stuck?
* [**Troubleshooting**](/help/troubleshooting.md): Step-by-step fixes for specific issues
* [**Known Limitations**](/help/known-limitations.md): Things that don't work yet (so you know it's not just you)
* [**Quickstart**](/start-here/quickstart-10-minutes.md): Start from the beginning with a guided walkthrough
* [**ProtoBot**](/protobot/overview.md): Ask the AI assistant for help directly in the app
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.protoboard.xyz/help/faq.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.