How to use Schematica

Your first board

Build a simple controller-and-sensor sketch in a few steps.

1. Name your board

   Open the editor and enter a title in the top-left field. If a board is already open, use Save to download a copy before choosing New.

2. Add two parts

   Search the left palette for MCU and add it to the canvas. Search for Temp sensor and place it beside the controller. Click or drag a palette item to add it.

3. Connect their ports

   Hover over a card to reveal its ports. Drag from the MCU's I2C port to the sensor's I2C port. The wire follows the parts when you move them.

4. Add the details

   Select a card or wire to edit it in Properties. Set labels, part numbers, rails and connection information that you know. Add the power and ground connections your design needs.

5. Review and save

   Press F to fit the diagram. Use Check to inspect findings, then Save to download an editable .schematica.json file. Export prepares an image or a handoff.

Find your way around

Hover over a toolbar icon to see its name and shortcut.

Top toolbar

Name the board, choose drawing tools, zoom, open examples, run checks, save and export.

Left palette

Search for parts, from embedded hardware to network, security, people and process-flow symbols, and create custom parts under My parts.

Canvas

Arrange cards and connections. Scroll to zoom; hold Space and drag to pan. F fits the whole drawing.

Properties

Select something on the canvas to edit its details. Select several items to reveal alignment and spacing controls.

Engineering

The connected-boxes icon beside BOM opens interfaces, requirements, revisions, saved views and review packages.

Press B to show or hide the parts palette, and P to show or hide the right panels. Click outside a text field before using editor shortcuts.

The Assistant is a movable panel. Drag its title bar anywhere on the page, or focus the title bar and use the arrow keys (Shift for larger moves). It remembers its position on this device; resizing or collapsing keeps a drag grip reachable.

Toolbar icon reference

Match each symbol to the top toolbar. Highlighted buttons mark the active tool or enabled display option; disabled buttons need an applicable selection or history. The board-title field names the current document.

Palette icon reference

Click a part to place it near the center of the view, or drag it to a location on the canvas. These are architecture symbols with default ports, not verified component specifications. Choose the real model and review its interface declarations before relying on a connection.

The categories run from embedded hardware (Compute through Automotive) to the parts of an IT estate: Endpoints, System & Cloud, Operating Systems, Network, Security & Edge, Facilities, People, Process Flow shapes and Threats. Hover over a tile to read what the part is for. Fold the categories you do not use; the Recent row keeps the parts you placed last. Search understands common aliases, so wifi, ap or firewall finds the right tile.

Every built-in part

Expand a category to see every icon, its purpose and its default ports. Search by name, category or port to narrow the list. Custom parts can use different icons and ports.

Panels and status icons

These controls appear in the floating panels, on selected items or inside dialogs. Read the label beside a symbol to distinguish actions that use the same shape.

Draw and connect

Parts and labels

Use the Select tool (V) to move cards. Double-click text to rename it, or edit the selected item in Properties. Use My parts → + New to define a reusable part with its own ports and fields.

Wires and buses

Drag between ports to connect them, or choose Draw wire (C). To connect with the keyboard, select a card and choose Connect… (or press Shift+C), choose both parts and ports, then Create connection.

Select a wire to change its bus, label, arrowheads, line style or traffic flow. Drag a selected endpoint handle to another port to reconnect it. Unlock a part if it is missing from the Connect ports form.

Zones, swimlanes and notes

Use Z to draw a zone around related parts, L to draw a swimlane, and N to add a note. Zones group an area; swimlanes organize stages or layers; notes explain assumptions and decisions.

Tidy the layout

Shift-click to select several items, then use Align, Distribute or Tidy spacing in Properties. Leave enough room between cards for ports and labels. Connections route around nearby cards and notes automatically.

Press K to lock or unlock selected items. Locked items keep their positions during dragging, alignment and deletion. Their other properties remain editable.

Open Check → Layout quality to find overlaps, obscured labels and wires crossing unrelated cards. Move the affected cards or adjust their spacing, then check again.

For a large board, open Explore (/) to search placed parts, filter by bus and change the reading detail. Reset exploration restores the view. These filters do not remove parts from the board.

Review the design

Check examines the information you have declared, including bus mismatches, address conflicts, missing connections and power estimates. Select a finding to locate the affected items.

Open Engineering → Interfaces to record a connection's limits and both endpoints' capabilities. Enter known direction, voltage, protocol, bandwidth and source references. Leave unknown values blank, and save the interface before moving on.

Checked

The supplied declarations pass the applicable comparisons.

Failed

The supplied declarations conflict. Inspect the finding and resolve it.

Unassessed

Information needed for assessment is missing.

Not applicable

The connection is excluded from interface assessment, such as a flow link.

Use Engineering → Requirements to allocate requirements and record verification methods and evidence. Save a named revision before a major change so you have a useful comparison baseline.

Save, recover and export

The working board is autosaved in this browser for this website. Use Save for a portable backup. The production website, static edition and localhost have separate browser storage.

The folder button beside the title lists the projects kept in this browser. Each has its own board, autosave and revisions; New project starts an empty board, choosing a project reloads the editor on it, and the menu shows when each was last saved to a file.

Engineering → Revisions saves and restores named snapshots on this device. Export important revisions to keep them outside browser storage. Save current work before loading a different board.

A share link contains the board's content. Give it only to people who should see that content. For a team discussion, use Team reviews in the palette; it appears when your server has that service enabled.

Present and record

Open Journey from the toolbar, frame an area and choose + Add step from current view. Select parts and use Link selection to keep the chapter linked to them. Add captions and reorder the steps.

Choose Present to start the tour. Arrow keys navigate, Space plays or pauses, and Escape exits. Interactive HTML exports keep the tour available offline.

Use Rec to record the canvas as video or GIF. Export → Loop GIF creates a short, seamless animation of the current board.

Use the assistant

Press A to open the assistant. Configure a provider, model, Base URL and API key, then Save and Test connection. Drawing, checks and exports work without the assistant.

Ask for a concrete change, review its preview and findings, then Apply changes or Discard draft. Applied changes can be undone. Keep Preview changes before applying enabled while learning.

Review this controller-and-sensor board. Identify missing interface declarations and explain what evidence I need. Leave unknown values blank.

You can attach text, PDF or DOCX sources. Selected extracted text is sent to your configured provider when you send a message. Remember the key on this device only when you want browser persistence. Provider use may be billed by that provider.

Explain an attack or incident

Ask the assistant to draw how an attack works. It builds the picture from threat parts, trust-boundary zones and labelled wires, then adds a step-by-step presentation.

1. Describe the attack

   Open Assistant (A) and describe the vulnerability or attack, or paste a link to an advisory. The assistant reads only the links you give it. Give it a CVE id and it draws the published record, using the CVE database configured on the server when there is one and otherwise CVE.org and NVD, and tells you the source.

2. Rebuild an incident from a log

   Attach a JSON log of timestamped actions (ts, actor, action, and optionally target and phase) and ask the assistant to show what happened. Each phase becomes a presentation chapter, with one stop per step in time order.

3. Review, edit and present

   Review the preview, then choose Apply changes. Edit the result like any other board, and choose Present to walk through the steps.

Draw how CVE-2021-44228 lets an attacker reach our logging server, then make a short presentation of the steps.

Replay an incident and mark conditions

A board rebuilt from a log shows Replay incident at the top left of the canvas. The replay plays the log on a clock: parts light up as the attacker reaches them, and each part takes on the condition its step leaves it in, such as suspicious, exploited, infected or exfiltrating, as a tag and a halo. Leaving the replay restores the board's own marks.

To record what happened to a part on any board, select it and choose a Condition in Properties. Examples → Enterprise Network: Phishing to Ransomware shows an office network drawn with the Endpoints, Network, Security & Edge, Facilities and People parts, with each host marked by its condition.

Build from a CVE, a write-up or a log

Build from a source, under Options and sources in the Assistant panel, builds these boards with no assistant provider configured. Nothing is sent to a model. Each button asks before replacing a board that has work on it, and one Undo brings the previous board back.

1. CVE id

   Choose CVE id, type an id such as CVE-2021-44228 and press Build. The record is fetched from CVE.org, with NVD for a missing score; only the id leaves the browser. The board shows the attacker in a zone named by the attack vector, a person when user interaction is required, the affected products with their version ranges, the flaw with its CWE and CVSS, and the impact on confidentiality, integrity and availability. A note holds the fix, the source, the references and any assumptions. Choose Present to step through Who acts, Boundary crossed, The flaw, Impact and Fix.

2. Write-up

   Choose Write-up, then paste the text or choose a file: an advisory, a blog post, a Markdown note or a script. The document is read for the CVE it names, whose record is fetched, and for the steps it describes: numbered or bulleted lines, lines after a shell prompt, request lines and commands inside code fences. The steps become quoted stops in a Steps from the write-up chapter on a proof-of-concept card. Nothing is run, resolved or tested. A document that names no CVE still draws, and every missing fact is listed as an assumption.

3. Incident log

   Choose Incident log and pick a JSON file of timestamped actions, the same shape the assistant accepts: an object with actions, or a bare array, where each action has ts, actor and action. The board is rebuilt in the browser with its timeline, and Replay incident appears at the top left of the canvas.

Appearance and language

Click the appearance icon to cycle Light → Dark → System. A sun, moon or monitor shows the current mode. System follows your operating system, and your choice is remembered on this device.

The 中文 / EN button switches the interface and this guide between English and Simplified Chinese. It does not translate text you wrote on your own board.

Export theme lets you choose a separate appearance for downloads. Automatic SVG follows the reader's system appearance; other automatic exports use your current appearance.

Keyboard shortcuts

Click outside text fields to use these shortcuts. The ? button in the editor opens the same reference. Ctrl is shown on Windows and Linux; ⌘ is shown on macOS.

Common questions

More guides

For detailed workflows and limits, continue with the documentation in the project repository.

• Guided first-review tutorial
• Full user guide: imports, comparisons and team reviews
• Editor reference and detailed limits
• Troubleshooting and recovery