TutuPCB · Quick start

Start from a dev board, sensor module, power board, or a blank board. You land straight in the editor — no upfront configuration.

Describe the board in one sentence: the MCU, how it is powered, what peripherals it drives. The more specific you are, the closer the part selection and pin assignment land.

Parts, footprints, and nets are three separate things. Changing a part number need not change the footprint, and changing a footprint need not rewire anything — AI touches only the layer you asked about.

Open any part to see its pinout and parameters. Swapping a part keeps the nets you already wired; pins that cannot be matched are listed explicitly instead of being quietly miswired.

Drag a part and the traces follow. Trace width follows the current it carries; power and ground pours, and decoupling caps placed close to their pins, are honoured during placement rather than patched afterwards.

Every change re-evaluates the board in your browser: parts that can't be built, routing conflicts and placement problems surface right there, each pointing at the component involved.

You export the four files a fab house takes directly: Gerber (layer artwork), Drill, BOM (bill of materials), and CPL (pick-and-place coordinates). No explanation needed — send the archive and get a quote.

Every save keeps a version: the Code page lets you open earlier ones and take the old content back. Published releases themselves are immutable — fix it and publish again.