Parts and Libraries (KiCad to Flux)
This section compares how to find, add, and manage parts in KiCad and Flux.
Import Your KiCad Project
Attach your KiCad project files, or a ZIP file of the project folder, to a message in the Chat panel. Ask Flux to import them. Flux creates a new project from the files.
To do it in the UI:
In Flux, select Import from the Flux menu, then select Project…. Upload your KiCad .kicad_pro, .kicad_sch, and .kicad_pcb files, a project folder, or a ZIP file. Each import creates a new project. It does not update an existing project or part.
Overview
Key differences when you move from KiCad to Flux:
KiCad manages global and local libraries separately. Flux has one library, and access depends on the part owner's permissions.
KiCad stores symbols and footprints separately. A Flux part contains a symbol and footprint.
Import a KiCad library into Flux. Import part libraries
Finding Parts in the Library
In KiCad
KiCad separates parts into Global and Project-specific libraries. And access to each library is managed in a project-by-project basis. Meaning every project potentially has access to a different set of libraries. This is configured in the “Set up symbol libraries” menu.

In Flux
Ask Flux to find parts in the library.
To do it in the UI:
Flux uses one library. Open it from the Library menu on the left side of a project.
The whole standard KiCad library is available in Flux. Browse all the available parts.
Part Access
The part owner sets access permissions. Read the sharing and permissions guide. The library shows:
Parts owned by others that have been made public.
Parts owned by others that have been shared with you.
Parts you own.
Adding a part to a project
Ask Flux to add parts to the project.
To do it in the UI:
Open a project and locate the Library menu on the left.
You can search and filter for parts using specific criteria, like "Contains Footprint" or MPN filters.
For commonly used parts like capacitors and inductors, you can use generic parts that you can update later with the correct MPN.
Drag and drop the part onto your canvas.
Start with a community part, then edit it for your design.
Adding Parts to the Library (Creating a Part)
In KiCad
Symbols and footprints are not necessarily related, other than when a footprint “is assigned to” a symbol. KiCad contains separate symbol and footprint libraries, which are created with different tools.
The process of creating a part looks something like:
Open the Symbol Editor and create your symbol.
Use the Footprint Editor to design the footprint.
Link the symbol to the footprint in your project

In Flux
Ask Flux to create a part. Flux creates the symbol, the footprint, and the properties in one part.
To do it in the UI:
Symbols and footprints are part of the same Flux part. Each part contains a schematic, a symbol, and a footprint.
Each part contains both a schematic and a symbol. This differs from KiCad. In this 0805 resistor example, the schematic contains two terminals. Flux terminals serve the same role as KiCad pins.
Parts have two “views” in Flux:
Internal view: Open a part to see its contents. Resistors, ICs, connectors, and most discrete parts contain only terminals.
External view: Place a part in a project to see its symbol.
Importing KiCad Libraries into Flux
Attach your KiCad library files to a message in the Chat panel and ask Flux to import them.
To do it in the UI:
You can import existing KiCad parts directly into Flux:
Open the Flux menu and select Import → Part….
Upload a
.kicad_sym,.kicad_mod, or legacy.libfile. You can also upload a.stepmodel.Understand that in Flux, the schematic is distinct from the symbol, offering more customization options.
Ask Flux
Ask Flux to do this work in your imported project.
Find replacement parts
Ask Flux to find replacements for parts that are obsolete, out of stock, or too expensive. Flux checks live stock and pricing from distributors and compares the datasheets before it changes a part.
Create parts from datasheets
Ask Flux to make a part that is not in the library. Flux reads the datasheet and creates the symbol, the footprint, and the pin mapping.
Next in the KiCad to Flux tutorial -> Schematics (KiCad to Flux)