How to share a KiCad project
Save the full project, choose who can open it and name the version you want reviewed. On BoardRepo, another engineer can inspect the board in the browser, download its source and continue in KiCad. You can also send a zip or use GitHub when that fits your workflow.
Option 1: send a zip
Zip the project folder and send it. Include the .kicad_pro, .kicad_sch, and .kicad_pcb files plus any project-local libraries and 3D models, or the design will open with missing symbols and footprints on the other side. The recipient needs KiCad installed, ideally the same major version. Useful when the recipient will edit locally; other reviewers need an exported preview or a browser viewer.
Option 2: push to GitHub
A Git repository gives you source history, branches and collaboration. Public repos can be cloned by anyone; private repos need repository access. GitHub does not natively draw KiCad design files, but your team can publish PDFs, images or previews generated by CI. See the full comparison in BoardRepo vs GitHub for KiCad.
Option 3: upload to BoardRepo
Upload the project zip (KiCad 6 or newer for rendered previews; the upload form shows current size limits). Review the retained files and upload exclusions. BoardRepo can produce schematic SVG and PDF, PCB view, extracted BOM as CSV, and gerbers with drill files generated from the actual sources when processing succeeds. A recipient with public or link-based access opens the available views in the browser without an account or CAD install. Public GitHub repos can also be imported directly, so the repo stays the source of truth and the board page links back to it.
Visibility is per project: Public, Unlisted, Password or Private. Unlisted share links carry an access token; their pages are excluded from listings and tell search engines not to index them. Successfully published versions retain their own source files. The Share control copies a link to the latest published version even while you are viewing an older one. For an exact revision, copy that complete sharing link and add v=3 for version 3: use ?v=3 when there is no query, or &v=3 after its existing token query. Keep the token intact; copying the address bar after opening a restricted board may omit it. Which option to pick, and what a share link does not protect you from, is in sharing a board privately.
Share from the KiCad editor
BoardRepo for KiCad adds Push and Pull to the editor. Push changed files to save a version with a message; share the board link for browser review. Pull brings the current saved remote version back into the local project. For an older revision, download that selected version from the board page. PCB Editor support requires KiCad 9.0.1 or newer, and Schematic Editor support requires KiCad 10. Include project-local libraries and review what is being uploaded before sharing.
A handoff between two engineers
- Save the project with its local libraries and a message explaining the change.
- Confirm the saved version's required previews are ready and share its exact version link.
- Have the other engineer inspect it and download that version's source. Pull is another option only when the current project is accessible through their plugin account.
- Coordinate who is editing. Save changed files as the next version, then compare the two revisions before the next handoff.
A public or sharing link permits browser reading and source downloads; it does not grant plugin access or permission to publish to your board. Plugin projects must be personally owned or accessible through authorized organization access. For shared publishing, arrange an organization editor grant; a viewer grant does not allow Push. Compare revisions explains sign-in, format compatibility and render requirements.
Bring an assistant into the workflow
For a team, an organization keeps the board and its history under shared ownership; admins assign viewing and editing access. Team setup is available through contact. An assistant can read separately approved board context, and a connection with personal save permission can add versions to boards you own. Compare and inspect the saved source before continuing in KiCad. For a team board, save through the web workspace or KiCad plugin with publishing access; assistant saving to organizations is planned. Follow the Claude and ChatGPT guide for setup and an inspection example. Sharing does not merge concurrent edits to the same CAD files.
Upload a project or see what a shared board looks like. Designing in Altium instead? Read how to share an Altium project.
Continue your work
Save your source and inspect its published revisions. Continue editing in your source design tool.
For KiCad projects, BoardRepo for KiCad lets you Push and Pull versions from the editor. Team workspaces bring shared source and board access together.