SparkFun KiCad Libraries: SparkFun parts and stock KiCad symbols in one place
SparkFun's KiCad Libraries
At a glance
- What is it?
- The SparkFun KiCad Libraries repository collects the parts SparkFun actually uses on its boards, mixing stock KiCad symbols, SparkFun footprints and open source 3D models, and it now installs through the KiCad Plugin and Content Manager. It is useful for hobbyists and engineers who need SparkFun footprints with manufacturability data attached.
- Who is it for?
- SparkFun KiCad Libraries fit a builder who wants SparkFun footprints, their 3D models and their internal part numbers without redrawing every part, especially one working in KiCad 10 where the PCM path is the supported route. It does not fit a team that needs a frozen, vendor-certified symbol set, since the README warns that the main branch is only generally proven and that footprints can be wrong.
- Can I use it commercially?
- Not without permission. GitHub finds no licence file in the repository, and without a licence all rights are reserved by default: you may read the code but not reuse it. Check the README, or ask the authors, before using it.
- Is it still maintained?
- Yes. The repository last received commits 4 days ago.
- What is it written in?
- Mainly Python, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on October 20, 2026, and from our analysis. They are not legal advice.
Editorial analysis
A parts library built from what SparkFun actually builds
The SparkFun KiCad Libraries hold the footprints, symbols and 3D models for the parts SparkFun uses, and the README describes them as a cultivated combination of KiCad stock parts, SparkFun-unique footprints and open-source 3D models. The audience is anyone laying out a board with SparkFun components in KiCad, typically a hobbyist or engineer who wants a known-good footprint and the matching 3D model instead of drawing one. What makes it more than a symbol dump is that the components carry internal part numbers, the PROD_ID style identifiers the README mentions, which SparkFun needs to make its SMD lines. That manufacturing data is why one generic capacitor symbol appears many times over with a different production ID attached to each instance, and it is the detail that makes these libraries interesting to a manufacturing-minded user rather than only to a hobbyist with a laptop.
Stock KiCad symbols by preference, original SparkFun footprints by habit
The README explains the method in unusual detail, which makes the design decisions legible. Rather than converting every previous SparkFun Eagle library to KiCad, the project adds new parts to these libraries as they are needed for new projects. The stated upside is clearing out old mistakes; the stated downside is opening the door to new ones, which the README puts bluntly as reader beware. For each new part, SparkFun decides whether to use a KiCad stock symbol, edit it for use, or create one from scratch, and it gives preference to the stock KiCad symbol. On the footprint side it gives heavy preference to the original SparkFun footprint but also looks at the stock KiCad footprint for inspiration, and it tries to follow the KiCad Library Conventions where that makes sense. In practice, a symbol from KiCad plus a SparkFun footprint plus a SparkFun 3D model is the common combination you get.
The bubble gum naming convention keeps lookalike parts apart
Because many components share a symbol, the naming scheme carries the differentiating data. The README lists the conventions used for these parts, and they are worth reading before you search the library. Capacitors are named by capacity, size, voltage and tolerance. Resistors follow resistance, size, optional wattage and optional tolerance. Inductors use inductance, size and maximum current, and LEDs use colour, size and optional wavelength. A name built from those four fields is therefore not a label, it is a specification, and the presence or absence of the optional trailing fields tells you which parameter the part is defined by. The result is that many visually identical parts carry different names, which looks like clutter in the library browser but is exactly what makes a bill of materials unambiguous.
Installing through the PCM, and the KiCad 10 restart that catches people out
Since the fall of 2025, releases of these libraries are available through the KiCad Plugin and Content Manager, which is the recommended route. The steps are short. Open the PCM, switch to the Libraries tab, type SparkFun into the search box, and press Install, which brings in the latest release. The catch is documented twice in the README: on KiCad 10, after installing through the PCM you must close KiCad and reopen it, and only then will the new libraries be visible. There is a second condition, which is that this method assumes your Library nickname prefix is still the default of PCM_. Any library installed through the PCM gets its symbol and footprint names prefixed with PCM_, and if you have cleared that prefix in the KiCad Preferences under Packages and Updates, the PCM path will not behave the way the documentation describes.
The without-pcm zip is the route when you cleared the nickname prefix
When the prefix has been cleared, the README points to a different asset on the releases page. Each release carries two zip file assets, and the one you want is the without-pcm file, because it ships the libraries without the PCM_ prefix. The procedure is to navigate to the releases page, download the without-pcm zip, and then use the Install from File option in the PCM to install it. The README also recommends clearing the prefix, confirming the change, closing KiCad and reopening it before installing the zip, and repeating the close and reopen after the install on KiCad 10. That sequence is a little fiddly, but it exists because the prefix is baked into the library names at install time rather than applied at draw time, and a mismatch between the two is what produces missing-footprint errors.
SPARKFUN_KICAD_LIBRARY is the path that keeps existing designs editable
Here is the part that trips up people copying a SparkFun schematic. Internally these libraries reference footprints and 3D models through an environment variable named SPARKFUN_KICAD_LIBRARY, and the release process converts that name into KICAD9_3RD_PARTY, which is what appears in the paths inside the release zip assets. At SparkFun the library is used as-is with the original SPARKFUN_KICAD_LIBRARY paths, so open-source designs from SparkFun carry those same paths. The consequence for you is specific: if you want to edit existing SparkFun schematics and board designs directly rather than merely place parts from the library, you need a manual install, either the zip download or a clone, configured with the original variable. The zip route is to download the current libraries with the Download ZIP option, unzip them somewhere convenient, rename the SparkFun-KiCad-Libraries-main folder to SparkFun-KiCad-Libraries, and in the KiCad Symbol Editor use Preferences, Configure Paths to add a new environment variable called SPARKFUN_KICAD_LIBRARY pointing at that folder.
Adding the symbol and footprint tables by hand after the manual install
The manual install continues in the editors. In the Symbol Editor, open Preferences, Manage Symbol Libraries, use the folder button to add an existing library to the table, navigate to the SparkFun-KiCad-Libraries symbols folder, select all the SparkFun-.kicad_sym symbol files and open them. The Footprint Editor repeats the pattern: Preferences, Manage Footprint Libraries, the folder button, Add existing (KiCad folder), then the SparkFun-KiCad-Libraries footprints folder, select everything and press Select Folder. The steps are verbose but they are the reason a manual install behaves differently from a PCM install. A PCM install registers the libraries for you and prefixes their names, while a manual install puts the files where the environment variable points, which is what keeps the paths inside downloaded SparkFun designs resolvable. A clone of the repository works the same way, with the repository layout of a symbols directory, a footprints directory and a 3dmodels directory at the top level.
Version 10 for KiCad 10, and an unclear licence
The release naming tracks the KiCad generation, which is unusual and useful to know. v9.0.0 is described as the initial release for the KiCad PCM and is dated 2025-10-17, and v10.0.0 is the release for the KiCad 10 PCM, dated 2026-08-20, with v1.2 recorded as the v9 snapshot before the PCM changes. The last push was on 2026-10-19, so work on the libraries continues even between tagged releases. The licence, however, is the weak point: the repository reports no standard licence identifier, and the README does not spell out terms, only noting that the components contain internal part numbers for ease of manufacture. Anyone planning to publish a board built on these footprints should check what SparkFun allows for the footprint files themselves, separately from the licence of any board you design with them.
Editorial conclusion
SparkFun KiCad Libraries fit a builder who wants SparkFun footprints, their 3D models and their internal part numbers without redrawing every part, especially one working in KiCad 10 where the PCM path is the supported route. It does not fit a team that needs a frozen, vendor-certified symbol set, since the README warns that the main branch is only generally proven and that footprints can be wrong. Before designing with it, install through the PCM and restart KiCad, then check the footprint of any part you have not placed before, and confirm the licence position yourself, since the repository reports no standard licence identifier.
Frequently asked questions
How do I install the SparkFun KiCad Libraries?
Since the fall of 2025 the libraries are available through the KiCad Plugin and Content Manager: open the PCM, select the Libraries tab, type SparkFun into the search box and press Install. On KiCad 10 you must close KiCad and reopen it before the new libraries become visible.
What is the without-pcm zip file for?
Each release attaches two zip assets, and the without-pcm one carries the libraries without the PCM_ library nickname prefix. It is the file to use if you cleared the prefix in the KiCad Preferences under Packages and Updates, installed through the PCM with Install from File.
What is SPARKFUN_KICAD_LIBRARY used for?
It is the environment variable the libraries use internally to reference footprints and 3D models, and the release process converts it to KICAD9_3RD_PARTY in the published zip assets. To edit existing SparkFun designs rather than only place parts, you need a manual install or clone configured with the original variable name.
Do the SparkFun footprints include manufacturing data?
Yes. The components contain internal part numbers of the PROD_ID form, which SparkFun needs to manufacture its SMD lines. That is why many components share an identical symbol while each carries its own production ID information.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/sparkfun-sparkfun-kicad-libraries)Was this useful?