Skip to the content
2 layersKi Test, the printed circuit board in 3D

If Bakery has helped you in any way please consider buying me a coffee

Copper layers
2
Thickness
1.6 mm
Parts
32
Nets
15
Pads
71
Tracks, vias
0, 0
Routed
Not yet
KiCad
KiCad 10.0 (file 20260206)
Created
13 Jan 2026
Updated
31 Oct 2026

Overview

Ki Test is an open-source printed circuit board by AdrianWest, from the AdrianWest/Bakery repository on GitHub, published under the GPL-3.0 licence. It is a 2-layer board with 32 parts on 15 nets.

Its parts include 18 diodes, 9 resistors, 3 capacitors and 1 connector.

README

README.md

Bakery KiCad Plugin banner

If Bakery has helped you in any way please consider buying me a coffee

Bakery - KiCad Plugin

Localize all KiCad symbols, footprints, 3D models, and datasheets to project libraries - They get Baked into your project


⚠️ IMPORTANT: Protect Your Design ⚠️

This plugin makes extensive changes to your schematic and PCB files.

Bakery creates a KiCad-compatible ZIP backup before it changes your project.

Why?

  • Bakery modifies .kicad_sch and .kicad_pcb files extensively
  • Bakery now supports restoring a previous design with KiCad's built-in Unarchive Project command
  • Each backup is saved as <project>-backups/<project>-YYYY-MM-DD_HHMMSS.zip
  • Version control is still recommended for complete history and day-to-day change tracking

Recommended: put your project under Git before running Bakery:

bash
cd /path/to/your/project
git init
git add .
git commit -m "Before Bakery localization"

Overview

Bakery is a KiCad plugin that automates the process of copying global library symbols, footprints, 3D models, and datasheets into project-local libraries. The plugin "bakes in" all external dependencies, converting references from global libraries to local project files. This ensures:

  • Project portability: No external library dependencies - everything is baked into your project
  • Version stability: Libraries won't change if global libraries are updated
  • Self-contained projects: All files and dependencies are contained in the project folder
  • Complete independence: Share projects without worrying about missing libraries

Installation

Option 1: Via KiCad Plugin Manager (Recommended)

  1. Open KiCad
  2. Go to Tools > Plugin and Content Manager
  3. Search for "Bakery"
  4. Click Install

Option 2: Install from ZIP File

  1. Download the latest release ZIP from GitHub Releases
  2. In KiCad, go to Tools > Plugin and Content Manager
  3. Click Install from File...
  4. Select the downloaded Bakery-x.x.x.zip file
  5. Click Open to install

Option 3: Manual Installation

  1. Download or clone this repository

  2. Copy the plugins folder contents to your KiCad plugins directory:

    • Windows: %USERPROFILE%\Documents\KiCad\10.0\scripting\plugins\Bakery\
    • Linux: ~/.kicad/10.0/scripting/plugins/Bakery/
    • Linux (Flatpak): ~/.var/app/org.kicad.KiCad/data/kicad/10.0/scripting/plugins/Bakery/
    • macOS: ~/Library/Preferences/kicad/10.0/scripting/plugins/Bakery/

    Note (Flatpak): KiCad installed via Flatpak runs in a sandbox and does not see ~/.kicad/.... Copy the plugin into the sandboxed data directory shown above, or KiCad will not detect it. After copying, fully quit KiCad (not just close the window) before relaunching so it rescans the plugins folder.

  3. Restart KiCad

Note: Bakery currently supports KiCad 10.x only. If you are still on KiCad 9.x (including Flatpak builds), use the last 9.x-compatible release, v1.1.0, instead of the current release.

How To Use Bakery

1. Prepare Your Project

  1. Save your KiCad project, schematic, and PCB.
  2. Close any other KiCad windows that have the project open.
  3. Confirm that the project is under version control if possible. Bakery also creates a timestamped KiCad ZIP backup before making changes.

2. Run Bakery

  1. Open the project's PCB in PCB Editor.
  2. Click the Bakery icon in the top toolbar, or select Tools > External Plugins > Bakery - Localize Symbols, Footprints, and 3d Models.
  3. Choose the local library and folder names in the configuration dialog.
  4. Confirm the operation and leave KiCad open while Bakery completes.

Bakery configuration dialog

Configuration Dialog Fields

These names control the project-local libraries and folders Bakery creates. The defaults are safe for most projects; change them only if you want different names in your KiCad project folder.

FieldWhat to enterWhat Bakery creates or updates
Local Footprint Library NameA KiCad library nickname, such as MyLibA local footprint library folder named MyLib.pretty and an fp-lib-table entry for it
Symbol Library NameA KiCad symbol library nickname, such as MySymbolsA local symbol library file named MySymbols.kicad_sym and a sym-lib-table entry for it
Symbol Directory NameA folder name, such as MySym or SymbolsThe folder that stores the local symbol library file
3D Models Directory NameA folder name, such as 3D ModelsThe folder that stores copied STEP/WRL model files
Datasheets Directory NameA folder name, such as Data_SheetsThe folder that stores downloaded or copied PDF datasheets
Place all library folders inside one folderCheck to group the output foldersPlaces the footprint, symbol, 3D model, and datasheet folders inside a single folder in the project
Parent Folder NameA folder name (default: Project_Lib); shown when grouping is checkedThe parent folder containing all the library folders

Click OK to start localization, Cancel to exit without changes, or Help to open the Bakery GitHub repository.

Bakery will:

  • Create <project>-backups/<project>-YYYY-MM-DD_HHMMSS.zip
  • Create local .pretty folders for footprints
  • Create local symbol library (.kicad_sym) in Symbols directory
  • Create local 3D Models folder for 3D models
  • Create local Data_Sheets folder for datasheets
  • Copy all used symbols, footprints, and their associated 3D models
  • Download datasheets from internet URLs and copy local datasheet files into the project datasheet folder
  • Scan and localize datasheet references from both schematic and PCB files
  • Update fp-lib-table and sym-lib-table to include local libraries
  • Update references in both PCB and schematic files to point to local libraries
  • Abort before making changes if the project backup cannot be created

3. Check the Result

  1. Review Bakery's log, warnings, and errors before closing KiCad.
  2. Open the schematic and PCB to confirm that symbols and footprints load correctly.
  3. Open the 3D Viewer to confirm copied 3D models render as expected.
  4. The project is now portable: its localized libraries, models, and datasheets are stored in the project folder.

Restore a Previous Design

Bakery backups are standard KiCad ZIP project archives. Restore a previous design at any time with KiCad's built-in Unarchive Project command:

  1. Close the current project.
  2. In the KiCad Project Manager, select File > Unarchive Project....
  3. Select the desired ZIP from the project's <project>-backups folder.
  4. Select a new, empty folder for the restored project. Do not restore over the current design until you have confirmed the backup is correct.
  5. Open the restored .kicad_pro file and verify the schematic and PCB.
  6. If it is correct, replace the current project only if needed.

For details, see the official KiCad documentation: Project archive and unarchive.

KiCad File menu highlighting Unarchive Project

Project Structure After Localization

text
YourProject/
├── YourProject.kicad_pro
├── YourProject.kicad_pcb
├── YourProject.kicad_sch
├── YourProject-backups/      # Timestamped pre-localization project archives
│   └── YourProject-YYYY-MM-DD_HHMMSS.zip
├── fp-lib-table              # Updated with local footprint library
├── sym-lib-table             # Updated with local symbol library
├── MyLib.pretty/             # Local footprint library
│   ├── Footprint1.kicad_mod
│   └── Footprint2.kicad_mod
├── Symbols/                  # Local symbol libraries
│   └── MySymbols.kicad_sym  # Local symbol library
├── 3D Models/                # Local 3D models
│   ├── model1.step
│   └── model2.wrl
└── Data_Sheets/              # Local datasheets
    ├── component1.pdf
    └── component2.pdf

Development

See .github/copilot-instructions.md for development guidelines and architecture details.

Project Architecture

text
Bakery/
├── __init__.py                 # Plugin registration and metadata
├── bakery_plugin.py            # Main plugin class (ActionPlugin interface)
├── constants.py                # Configuration constants and messages
├── ui_components.py            # Logger window and configuration dialog
├── footprint_localizer.py      # Footprint and 3D model localization
├── symbol_localizer.py         # Symbol localization
├── data_sheet_localizer.py     # Datasheet localization (download/copy/update)
├── library_manager.py          # Footprint library table management
├── sexpr_parser.py             # S-expression parser
├── utils.py                    # Shared utility functions
└── metadata.json               # Plugin metadata for KiCad Plugin Manager

Features

✅ Symbol Localization: Automatically copies all symbols from global libraries to your project

✅ Footprint Localization: Automatically copies all footprints from global libraries to your project

✅ 3D Model Localization: Copies associated 3D models and updates paths

✅ Datasheet Localization: Downloads datasheets from internet URLs or copies local PDF files to your project; updates all references to use portable ${KIPRJMOD} paths

✅ Automatic Reference Updates: Updates PCB, schematics, and library tables

✅ Dual Scanning: Scans both PCB and schematic files for complete coverage

✅ Automatic Project Backup: Creates a KiCad-compatible timestamped ZIP before changing project files

✅ Progress Tracking: Visual progress bar with step-by-step status

✅ Detailed Logging: Separate panes for info, warnings, and errors

✅ Configurable: Choose local library and directory names

✅ Path Safety: Validates all file operations to prevent data loss

✅ KiCad 10 Support: Built for KiCad version 10

Requirements

  • KiCad 10.x
  • Python 3.x (bundled with KiCad)
  • wxPython (bundled with KiCad)

Configuration

When you run Bakery, you can configure:

  • Local Footprint Library Name: Name for the local footprint library (default: "MyLib")
  • Symbol Library Name: Name for the local symbol library file (default: "MySymbols")
  • Symbol Directory Name: Name for the symbol library directory (default: "Symbols")
  • 3D Models Folder: Name for the 3D models folder (default: "3D Models")
  • Datasheets Directory Name: Name for the local datasheets folder (default: "Data_Sheets")
  • Automatic Project Backup: Mandatory and created in <project>-backups

License

GNU General Public License v3.0 - see LICENSE file

Contributing

Contributions welcome! Please open an issue or pull request.

Please note that this project is released with a Code of Conduct. By participating in this project you agree to abide by its terms.

Roadmap

Version 2.2.0 - Current Release

  • Optional grouping of library folders inside a named parent folder (default: Project_Lib)
  • KiCad 10 project support, including projects that still reference 9.x global libraries
  • Localization of symbols, footprints, 3D models, and datasheets into project-local libraries
  • Collision-safe local names and filenames for symbols, footprints, 3D models, and datasheets
  • Mandatory KiCad-compatible, timestamped ZIP backup before localization
  • Restore previous designs through KiCad's File > Unarchive Project... command
  • Safe repeat runs that preserve local ${KIPRJMOD} 3D model paths
  • Detection and user-visible warnings for unresolved local symbol references
  • Recursive hierarchical-schematic processing and dual PCB/schematic scanning
  • Automated unit tests and Windows KiCad 10 functional tests that reopen both the localized PCB and root schematic

Planned for Future Versions

  • KiCad 11 compatibility review and support
  • Additional localization and recovery improvements based on user feedback
  • Expanded functional-test coverage for new KiCad versions and project configurations

Testing

Unit Tests

The unit suite uses Python's built-in unittest framework and mocks the KiCad APIs where necessary. From the repository root:

powershell
python "Unit Test\run_tests.py"             # Run all unit tests
python "Unit Test\run_tests.py" --verbose   # Show each test name
python "Unit Test\run_tests.py" --list      # List discovered test modules
python "Unit Test\run_tests.py" --coverage  # Write terminal and HTML coverage reports

--coverage requires the optional coverage package:

powershell
python -m pip install coverage

The suite covers the plugin entry point, localization modules, backup and configuration handling, utilities, library management, and S-expression parsing. See Unit Test/README.md for test-specific details.

Automated Functional Tests

The functional suite drives a real KiCad 10 installation through its UI. It restores all four fixture projects, installs the plugin, runs Bakery, checks the localized project files, verifies a second run makes no unintended changes, and reopens the localized PCB and root schematic in KiCad.

Requirements

  • Windows with KiCad 10 installed
  • Python 3.x
  • pywinauto, pywin32, and psutil
  • No open pcbnew.exe or Bakery plugin process

Install the Python test dependencies once:

powershell
python -m pip install pywinauto pywin32 psutil

From the repository root, run the complete suite or selected fixtures:

powershell
# Run FT-01 through FT-04
python "Functional Test\functional_suite\run_functional_tests.py"

# Run only selected fixtures while iterating
python "Functional Test\functional_suite\run_functional_tests.py" --fixtures FT-01,FT-03

# Run one localization pass only, without the second-run or PCB/schematic reopen checks
python "Functional Test\functional_suite\run_functional_tests.py" --skip-idempotence --skip-reopen

Test workspace files are created under C:\GIT_HUB\testing. Each run writes junit.xml, summary.json, environment.json, and report.md to C:\GIT_HUB\testing\results\<timestamp>\. Datasheet download failures and the fixtures' deliberately missing references are asserted as expected conditions; unexpected localization, PCB reopen, or schematic reopen failures cause a nonzero exit code.

See Functional Test/functional_suite/README.md for the fixture matrix, assertions, expected issues, and report details.

Parts

32
QtyValueFootprintReferences
181N4004Diode_THT:D_DO-41_SOD81_P10.16mm_HorizontalD1, D2, D3, D4, D5, D6, D7, D10, D11, D12, D13, D14, D15, D16, D17, D18 +2
91KResistor_SMD:R_4020_10251Metric_Pad1.65x5.30mm_HandSolderR1, R2, R3, R4, R5, R6, R7, R8, R9
3C_USCapacitor_SMD:CP_Elec_18x17.5C1, C2, C3
1Conn_01x01Connector_Phoenix_MC:PhoenixContact_MCV_1,5_4-GF-3.81_1x04_P3.81mm_Vertical_ThreadedFlange_MountHoleJ1

The 31 most common of 32 parts.

More from AdrianWest/Bakery

2
  • 2 layersKi Test, the printed circuit board in 3D

    Ki Test

    AdrianWest/Bakery

    If Bakery has helped you in any way please consider buying me a coffee

    31 parts15GPL-3.0
  • 2 layers5V REG 20A, the printed circuit board in 3D

    5V REG 20A

    AdrianWest/Bakery

    If Bakery has helped you in any way please consider buying me a coffee

    27 parts15GPL-3.0

Similar boards

  • 2 layers50 × 23.2 mmAnalog, the printed circuit board in 3D

    Analog

    hoglet67/RGBtoHDMI

    Bare-metal Raspberry Pi project that provides pixel-perfect sampling of Retro Computer RGB/YUV video and conversion to HDMI

    32 parts1kGPL-3.0
  • 2 layers136.8 × 54.2 mmRetropie zero, the printed circuit board in 3D

    Retropie zero

    hackclub/OnBoard

    💡 Join 1,000 teenagers and make your first PCB with a $100 grant!

    32 parts915
  • 2 layersMooltipass top, the printed circuit board in 3D

    Mooltipass top

    limpkin/mooltipass

    Github repository dedicated to the mooltipass project

    32 parts531
  • 2 layers16 × 20 mmESPKey, the printed circuit board in 3D

    ESPKey

    octosavvi/ESPKey

    Wiegand data logger, replay device and micro door-controller

    32 parts353GPL-2.0
  • 2 layers82 × 40.9 mmDisplay7447, the printed circuit board in 3D

    Display7447

    zmaker/arduino_cookbook

    gli sketch del nuovo progetto Arduino Cookbook e dei video di YouTube

    32 parts269
  • 2 layers40 × 38 mmShield, the printed circuit board in 3D

    Shield

    murexrobotics/electrical

    Highly integrated electronics design and printed circuit boards (PCBs) for the MATE ROV Competition. Attempt the impossible.

    32 parts192MIT
  • 2 layers47 × 39 mmQrss clock tx, the printed circuit board in 3D

    Qrss clock tx

    swharden/AVR-projects

    A collection of standalone AVR projects written in C

    32 parts184MIT
  • 2 layers30.9 × 63 mmStm32-io extend, the printed circuit board in 3D

    Stm32-io extend

    hardenedlinux/cheap-pcb

    Cheap PCB: Better understanding the current status of hardware supply chain

    32 parts170CC0-1.0

Questions

What parts does the Ki Test use?

32 parts. The full list of its parts is on this page, with links to each part's symbol and footprint where PCBKit's library has them.

Where can I download the Ki Test KiCad files?

From the AdrianWest/Bakery repository on GitHub, at the commit this page was made from: the board is Functional Test/Ki-Test 01-10 - Backup/Ki-Test.kicad_pcb and its schematic Functional Test/Ki-Test 01-09 - Backup/Diodes.kicad_sch. PCBKit opens the board in the browser, with nothing to install.

Can I use the Ki Test design in my own project?

Its repository publishes it under the GPL-3.0 licence: you may reuse it on that licence's terms (keep the author's notice, and for a copyleft licence share your changes alike).