Exports and files
Every file a fab, an assembler or KiCad needs is saved with the version. You can download one version's files, or the whole project as one zip.
One version's files
The Export button in the header groups the files by who they are for. The version menu lists every version's files too, and the HTTP API serves each file at the top of the version.
| File | What it is |
|---|---|
gerbers.zip | The fab files only: Gerbers, drill, BOM and CPL. A four-layer board's inner layers are in it. Nothing the app needs, so you can send it as it is. |
<board>.kicad_pcb | A KiCad board you can open and edit. Its footprints point at models/<lcsc>.wrl beside it. |
<board>.kicad_pro | The KiCad project: the design rules the board was built to, so KiCad's DRC checks the same rules |
<board>.kicad_sch | The schematic, as the workbench draws it, in KiCad 7's format. KiCad 7, 8, 9 and 10 open it. Each part carries its LCSC code as a hidden field. |
<board>-F_Cu.gtl and the other layers | The individual Gerber layers. A four-layer board adds <board>-In1_Cu.g1 and <board>-In2_Cu.g2. Fab files lists them all. |
<board>-BOM.csv, <board>-CPL.csv | JLCPCB's assembly files: the parts list and where each part goes |
<board>.dsn | The board as the router was given it, in Specctra format |
Standalone page (inspector.html) | The workbench for this board, in one file that opens with no server. Chat and history are off. It loads three.js and fonts from a CDN. |
board.svg | A preview, also used as the project thumbnail |
design.json | The design, before parts were resolved, with its constraints. Import it to rebuild the board without a model. |
board.json | Everything the viewer draws: parts, pads, nets, copper, ERC, stock. See board.json. |
sim.json | The simulation traces the Scope tab draws, when the board was simulated |
meshes.json | The vendor 3D models the viewer draws |
models/*.wrl | The vendor 3D models KiCad draws. They sit in a folder, so they come only in the project zip. |
3D models in KiCad
A .kicad_pcb downloaded on its own opens without its 3D models. To see the
parts in KiCad's 3D viewer, export the whole project and open the version's
folder from the zip.
KiCad's own netlist of the .kicad_sch matches the design net for net, and its
ERC finds no errors. See KiCad and 3D models.
The browser keeps a version's files for a day. Add ?dl=1 to any file URL to
download it instead of opening it in the browser.
The whole project
A project zip holds every version, the unbuilt draft, the conversation, the labels, the notes and the saved variations. It comes back as one project.
| How | |
|---|---|
| Export | Export .zip on the project's disc on the home page, or Every version and the thread in the workbench's Export menu. API: GET /api/projects/<slug>/export.zip. |
| Leave the chat out | Add ?chat=0. Each version still carries the prompt that made it. |
| Import | Open a file on the projects page, or drop the zip anywhere on it. API: POST /api/projects/import. |
| Rename on import | Fill the name field. A name already in use gets a suffix. |
The zip is the project directory as it sits on disk (see
Projects on disk). So unzipping into
projects/ also imports it, and a folder zipped by hand also works.
- A wrapper folder,
__MACOSXand.DS_Storeare ignored. - The
.workbuild directory and any unaccepted proposal are left out. - A project zip may be up to 256 MB. The rest of the API stops at 8 MB.
- The 256 MB allowance is for a request the server already trusts. That is one with the login cookie or the access token. It is also one from this machine, unless the server runs behind a proxy. With access control off, every request is trusted. Any other import stops at 8 MB.
A bad zip changes nothing. A zip that is not a project is refused, naming
the file or field it stopped at. The zip is read in full and unpacked beside the
projects first. It moves into place only when everything checks out. A project
from a newer soldermask is refused with 409.
A design.json keeps its constraints. An exported design.json carries the
pins, sides and rules of its version.
- Imported into a project with no constraints of its own, the file's are kept. The reply says so, for example Kept the file's constraints: 1 pinned part, rules router=krt.
- Imported into a project that has its own, the project's win. The reply says the file's were set aside.
Before you order
Check that the workbench's poll reads GO. Then read the Advisories group in its findings, and What is not guaranteed. The Gerbers are read back with an independent library, and the KiCad file is checked against the placement. But a borrowed footprint or pinout, or a part the model was unsure of, is reported in the advisories and nowhere else.
Versions and history
Every build saves a version, and a version's design and fab files never change. You can open, compare, label and fork any of them.
Builds and live sync
A build runs on the server as a job, so it keeps going when you close the tab. Two devices open on the same project follow each other live.