⚡ A linter for hardware design

Your schematic looks fine.
Electrace tells you if it actually is.

Assemble your design from functional blocks. Electrace runs deterministic checks on every edit — and every finding names the exact part and shows the arithmetic behind it. No simulation. No black box. Nothing guessed.

Free, no account, no card. Export to KiCad when you're done.
buck-supply.elec — Electrace⬣ 1 error — over-voltage
✦ U1 — buck controller. Holds 5 V from a 9–18 V input; R1/R2 set the voltage.
24 V into U1 — rated 18 V max.VIN net, highlighted.
Power Entrydisc
24 V DC in
Buck RegulatorIC
9–18 V → 5 V · 3 A
U1
+5 V

A live Electrace design — hover a block to see what it does. And the linter just caught a 24 V brick feeding an 18 V-max regulator, before it shipped.

Runs in your browser·No simulation, no SPICE·Checks every edit in milliseconds·Every finding shows its math

Other tools stay silent — or just guess.

Electrace is the one that shows you why.

What it catches

It names the part. It shows the math. It tells you the fix.

Thermal

This LDO drops 12 V → 3.3 V at 500 mA. That's 4.35 W burning inside a SOT-223 rated for ~2 — it'll cook. Switch to a buck, or budget a heatsink.

Power budget

Your VBUS loads add up to 2.4 A on a rail you've budgeted for 2. That's 120% — something's browning out or getting hot.

Signal integrity

I²C rise time τ ≈ 850 ns — too slow for 400 kHz (the limit is 300). Drop the pull-ups to 2.2 kΩ and you're at ~190 ns.

Polarity

C4 is in backwards — its + pin is sitting on ground.

Why you can trust it

The most useful thing a tool can do is tell you when it can't trust its own answer.

We asked Sparky for the standby draw on a battery design — but the design hadn't declared its sleep-state current, so the solver had nothing to measure. A lesser tool would have reported “0 mA” and called it a win. A chatbot would have invented a plausible figure. Sparky did neither.

Sparky

The standby analysis found no computable always-on draw — meaning either the design truly has no always-on leakage, dividers, or pull-ups, orthe sleep-current declarations aren't detailed enough to calculate it. So the tool can't produce a meaningful battery-life estimate yet. If your MCU sleep current is known, declare it in the block — then standby draw can compute it.

It would rather be honest than impressive — which is exactly why you can believe it when it is impressive.

Build a design and watch it check itself →
How it works

Build it. Watch it check itself.

Self-explaining blocks

Authored intent, not guesses. Every block says what it does and why.

Drill into anything

Double-click into a block's real schematic — discrete or IC, every part labeled.

Linting, not SPICE

Voltage and current follow every wire — over-voltage, blown budgets, broken isolation, and overloaded connector pins get caught with the where and the why.

Transparency

Open any block.
Read every part.

The one IC stops being a mystery — you see exactly what surrounds it, and why.

  • A plain-language reason on every part.
  • ANSI or IEC symbols — your choice.
VIN+5 VU1R1 39k↳ sets 5 V
Sparky

An AI assistant
that doesn't get to guess.

Didn't we just say copilots guess? They do — because nothing checks them. Sparky is different by construction: everything it draws goes through the same deterministic linter as your own work. Every wire resolved, every budget recomputed, every claim checkable.

  • Builds from real, spec'd blocks — with a real BOM, not invented part numbers.
  • When it's wrong, the checker says so. Out loud, on the canvas.
  • Explains every choice in plain language — it's a tutor, not an oracle.
Sparky
"Add battery charging for a single Li-ion cell."
Placed Li-ion Charger (1 cell) — 4.2 V CV, 580 mA via the PROG resistor — and wired VBUS → IN, BAT → your load. Running checks…
14 nets resolved · budgets recomputed · 0 errors
+5 Vrail · connected
GNDground · connected
STATUS⚠ not wired
Typed nets

Nothing
forgotten.

Connect net-to-net — 5 V to 5 V, ground to ground. Leave one dangling and Electrace tells you, right there.

Voltage propagationCurrent budgetsShorts & polarityGalvanic isolationSignal integrityConnector ratingsRegulator thermalPCB DRC
Why Electrace

Not guessing. Not SPICE.
Not locked in.

AI copilots guess
We show what's declared.
Generators do it for you
We make you understand it.
Simulators need setup
Instant arithmetic checks.
Vendor tools sell silicon
Vendor-neutral, always.
And when you're done

Design it. Understand it. Build it.

Electrace is a free, browser-based circuit and PCB design tool built around one idea: you should be able to see inside every circuityou build. Every block carries its real schematic and the reasoning behind every part; the checking engine follows voltage and current through every wire and tells you where — and why — something won't work. Draw the schematic, lay out the board, export to KiCad, order the parts. No simulation setup, no install, no vendor lock-in.

Design with blocksLay out the PCBBuild it or get it made
Questions
Does Electrace simulate my circuit?

No. Electrace runs deterministic structural checks — typed nets, power budgets, and signal-integrity and isolation rules — not a SPICE simulation. A clean result means the design is structurally sane, not lab-validated.

Is Electrace free?

Yes. The full understand-your-circuit loop is free on the Hobby plan: blocks, live checks, BOM, PCB, and KiCad export. Signal-integrity and isolation analysis are part of Pro.

Can I export to KiCad?

Yes. Electrace exports the netlist and the PCB to KiCad, so it drops into a standard hardware workflow.

How is it different from a normal schematic editor?

Every block explains what it does and why, and the checker shows where and why a problem exists on your actual design — not just that something is wrong.

Do I need to install anything?

No. Electrace runs entirely in your browser.

Early access

Start understanding
your circuits.

Built by US Nylon · no spam, just launch news