// everything PartFolio does
From catalog to workshop, all the way to KiCad.
A shareable component base: custom fields, stock, manufacturing, symbols and footprints versioned in git, and direct reading by KiCad. Here are the details.
- 15key features
- 5chapters, from catalog to AI
- 1file to connect KiCad
ORGANIZE
01 · YOUR BASE
A library, your component base
A library is your own base: you fill it, you keep it, you come back to it, you test your builds. Organize it however you want, by project, by supplier, or all in one place. Each library is isolated, lives in your organization, and switches in one click from the selector.
- Your base, built and kept over time
- Organize it your way, or not at all
- Isolated and yours: fork, copy, export
02 · ADAPT
Fields tailored to your components
Add your own fields, define controlled value lists, and choose which columns are displayed. The base fits the way you work.
- Custom fields per library
- Value lists as a controlled vocabulary
- Displayed columns, your pick
03 · DOCUMENT
The datasheet, one click away
Attach the PDF datasheet to each component, or a simple external link. Instant opening, storage on a dedicated volume.
- Uploaded PDF or external link
- Viewable in one click from the list
- Included in the .zip export
WORKSHOP
04 · TRACK
Stock and locations, in real time
Track the quantities of each component, where they are, and what goes in and out. The inventory view shows you the state of the workshop at a glance.
- Quantities and locations in real time
- Per-component alert thresholds
- Movement log
05 · BUILD
From KiCad BOM to workbench
Import the bill of materials (BOM) exported by KiCad: PartFolio checks available stock, flags shortages, estimates the cost, and prepares the picking list by location.
- KiCad BOM import (CSV)
- Stock check, shortages and cost
- Picking list sorted by location
KICAD
06 · CONNECT
KiCad reads your components live
One token, one .kicad_httplib file, and KiCad queries your library through the HTTP API in real time. Nothing to export, nothing to sync.
- Ready-to-use .kicad_httplib file
- Encrypted API token (AES-256-GCM)
- Real-time reads, database never exposed
07 · VERSION
Symbols and footprints, versioned in git
Each library ships its own git repository of symbols and footprints. KiCad clones it directly, and every change is a commit: the history of your .kicad_sym and .pretty files is always there.
- One git repository per library, clonable in KiCad
- .kicad_sym and .pretty files under version control
- Read-only token (clone) or read/write (push)
08 · VISUALIZE
Your symbols, drawn in PartFolio
PartFolio renders your symbols and footprints: thumbnails in the component list, and a live preview in the record while you type the KiCad mapping, with autocomplete of repository references.
- Symbol thumbnails in the list
- Live preview of the symbol / footprint mapping
- Reference autocomplete, ✓ when known to the repository
SHARE
09 · SHARE
Members, three clear roles
Invite your team to a library and give everyone the right level of access. Write actions are hidden for a reader.
- Owner: members, tokens, rename, delete
- Editor: data and token CRUD
- Reader: read access and KiCad usage
10 · OPEN
Share with another organization
Your library can serve beyond your organization: invite an account from another organization by email. They accept the invitation, then access the library with the role you chose, Reader or Editor, never more: ownership stays with you.
- Email invitation, accepted by the invitee before any access
- Reader or Editor: ownership stays within your organization
- External members visible, role editable, access revocable
11 · STRUCTURE
One organization, your accounts, your quotas
Your libraries live in your organization: invite accounts, manage who accesses what, and track your plan's quotas.
- Accounts invited at the organization level
- Libraries attached to the organization
- Quotas based on your plan
12 · FORK
Fork a library
Start from an existing library to create your own: a complete, independent copy, in one click. Available even with read access.
- Complete copy: components, lists, records
- An independent library as the result
- Open to any member, even Reader
13 · REUSE
Copy between libraries, without duplicates
Transfer components from one library to another. A preview detects duplicates before writing, within the limits of your permissions.
- Preview before applying
- Automatic deduplication
- Member of the source, write access on the target
14 · BACK UP
Export, import, migrate as .zip
Take a whole library with you in a .zip archive: components, reference lists and PDFs. Re-import into a new library or an existing one, with a preview before applying.
- Complete archive: data + datasheets
- Import into a new or an existing library
- Stage · preview · apply steps
ASSIST
15 · CHAT NEWBETA
Your database, driven by AI
Plug an MCP client (Claude) into your library with an API token. The assistant reads your components, your lists and your stock, and answers in natural language: "my N-channel MOSFETs in SOT-23 available in stock", "which records have no datasheet". It spots inconsistencies, and will soon fill in fields itself, with references resolved server-side.
- Browse in natural language, no queries to write
- Consistency checks: empty fields, duplicates, missing datasheets
- Per-library token, read or write scope, strict isolation
Ready to connect KiCad?
Create your library, add your components and their stock, and KiCad reads them live through the HTTP API.