# Projects and Files

Use a WireFrame project to keep schematics, PCB documents, and project libraries together. A project can contain multiple schematics and PCBs, while a standalone document can be opened without joining a project.

## Create a project

1. Select **File → New → New Project (.prjxml)...**.
2. Choose the folder for the project (**Select Folder for New Project**).
3. In **Create New Project**, check **Selected Path**, type the project name, and select **Create**.

WireFrame writes `<name>.prjxml` and an empty project library folder `lib_<name>/` into that folder, then opens the project.

Keep the project and its documents in a dedicated folder. This makes relative library and model paths easier to move, archive, and share.

### Short video — Create a new project

<video controls muted playsinline preload="metadata" src="assets/wf/docs/projects/create-a-new-project.mp4" title="File → New → New Project, pick a folder, name it, Create"></video>
## Open a project or document

| What you want to open | Command |
|---|---|
| WireFrame project | **File → Open Project (.prjxml)...** (++ctrl+p++) |
| Project, schematic, or PCB | **File → Open File...** (++ctrl+o++ opens a schematic or PCB) |
| KiCad project | **File → Import → KiCad Project (.kicad_pro, .pro)...** |

Opening a `.prjxml` restores its linked documents and project structure. Opening a `.schxml` or `.pcbxml` directly adds it as a standalone file for the current session.

### Image — Project Structure with multiple documents

![Project Structure of the hexapod robot's main board: the root sheet, eight sub-sheets and one PCB](assets/wf/docs/projects/project-structure-with-multiple-documents.png)
## Add and organize documents

Right-click the project in **Project Structure** and choose **Add New Schematic** or **Add New PCB**. Save a newly created document before relying on it as a project member. Right-click a file for **Rename**, **Exclude from Project**, **Remove from List** (the file stays on disk), **Delete...** (removes it from disk — cannot be undone), and, for a PCB, **Set Root Schematic ▸** — see [Project Structure](ui-overview.md#project-structure).

**File → New → New Schematic (.schxml)** and **New PCB (.pcbxml)** create a document directly. **File → Close Document** closes the active document; **File → Close Project** closes the project without deleting any of its files.

| Document | Extension | Contains |
|---|---|---|
| Project | `.prjxml` | Linked schematics, PCBs, and library references |
| Schematic | `.schxml` | Symbols, wires, labels, annotations, and page settings |
| PCB | `.pcbxml` | Footprints, nets, traces, vias, zones, layers, and design rules |

Use **File → Save** for the active document and **File → Save As** when you need a new path. Closing a project does not delete its documents.

## Update a schematic to PCB

Before updating a PCB:

1. Complete the schematic connectivity.
2. Assign a valid footprint to every physical component.
3. Run ERC and resolve critical issues.
4. With a schematic of the project active, select **Tools → Update Schematic to PCB** (a submenu lists the boards when the project has more than one). A project is required — a standalone schematic cannot be converted.
5. Review new or changed footprints and the ratsnest before routing.

The update collects every sheet of the design from the top sheet down, keeps footprints that are already placed (position, rotation, and side), removes footprints whose component is gone from the schematic, places new footprints in a grid, updates the nets, and saves the PCB. Running it again after schematic changes is safe. See [Footprints and Placement](pcb/footprints-and-placement.md#from-the-schematic-the-normal-way).

!!! warning "Footprints are required"
    A physical component without a valid footprint cannot be placed correctly on the PCB. Resolve missing symbols, footprints, and pin-count mismatches in Component Review or the library editors before continuing.

### Short video — Update schematic to PCB

<video controls muted playsinline preload="metadata" src="assets/wf/docs/projects/update-schematic-to-pcb.mp4" title="Tools → Update Schematic to PCB, then the board"></video>
## Import a KiCad project

1. Select **File → Import → KiCad Project (.kicad_pro, .pro)...**.
2. Select the KiCad project file.
3. Keep WireFrame open while the progress overlay reports each import stage. The converted WireFrame project is written into the KiCad project's folder.
4. Review the resulting project, schematics, PCB, and library assignments.
5. Save the converted WireFrame documents.

After import, check:

- sheet and document count;
- symbol values and references;
- net labels, power symbols, and connectivity;
- footprint side, rotation, and pad numbering;
- board outline, zones, vias, and design rules;
- library and 3D model paths.

### Short video — Import a KiCad project

<video controls muted playsinline preload="metadata" src="assets/wf/docs/projects/import-a-kicad-project.mp4" title="File → Import → KiCad Project, then the imported project"></video>
## Import scope

The project importer reads KiCad `.kicad_pro` and legacy `.pro` projects, and Altium Designer projects through **File → Import → Altium Project (.PrjPcb, .SchDoc, .PcbDoc, .zip)...**. Eagle projects are not imported — open them in KiCad first.

A WireFrame project can also be written out as a KiCad, Altium Designer or EasyEDA project. See [Import and Export](import-export.md).

Altium and KiCad library files are handled through **View → Local Library Manager**. See [Library Import and Management](libraries/library-converter.md).

## Import a PCB outline

With a PCB active, select **File → Import → CAD Outline (.svg / .dxf)...** and tick **Import as BOARD OUTLINE** to make the drawing the board's shape — outline, cutouts, and mounting holes. The dialog shows the board size and any problems before you import. See [Board Shape and Outline](pcb/board-outline.md).

!!! note
    DXF files are read only with **Import as BOARD OUTLINE** ticked. Plain graphics import (Edge.Cuts, silk, copper) reads SVG.

## Session restoration

WireFrame remembers open projects, standalone documents, panel layout, and recent folders. On the next launch, confirm that restored documents still resolve their linked libraries and models.

If the previous session should not be restored, close its documents and project before exiting, or turn off **Preferences → Workspace → Restore on launch**.

## See also

- [Getting Started](getting-started.md)
- [Configuration and Session Storage](reference/config-and-session.md)
- [File Formats](reference/file-formats.md)
- [Import and Export](import-export.md)
- [Library Import and Management](libraries/library-converter.md)
