KiCad in the Browser

KiCad, a PCB EDA suite is now working in a browser, you can try it at the link, there's a demo project or you can bring your own. Firefox is best, Chrome is good, Safari is "working".We’re Emergence Engineering, a dev shop from Hungary, mostly working with rich text editors, CRDTs. PCBJam started as my (Viktor, CTO, ex-electrical engineer) hobby project but as time went on I put more and more energy into it, and a product started shaping up in my head, in the last few months we’ve started to focus on this project a bit more, and this is the first MVP~ish result.This project is a ton of fun, ton of learning, ton of improvements over improvements:- I thought there must be ways to emulate the PCB canvas OpenGL code on the web. And yes, there are a lot of ways, all of them very buggy. Turns out it’s faster to just write WebGL code that works with KiCad’s Graphics Abstraction Layer if you add the right intermediate debugging steps. I (with Claude) implemented the features and compared them to native at every step, then the app loaded up the first time and just worked. I spent weeks hunting weird emulation bugs before that.- There was an old wxWidgets web port as a starting point that helped a lot, bringing it up to the level KiCad needed is a long (and still ongoing) task. Thanks ahilss!- Pthreads on the web: with Emscripten it’s possible to port multithreaded apps (used by DRC, software 3D renderer). A lot of Emscripten features (Asyncify, Pthreads, native exceptions) are in a war with each other, but it’s possible.- Asyncify with native exceptions: Asyncify (used to make the WASM code suspend then call into the JS land, emulating blocking C++ calls by rewriting the WASM directly) is not compatible with native exceptions, even on the latest Binaryen version it can’t suspend inside catch arms. If you write a new Binaryen pass then it can, making the bundle 30-40% smaller and the app load in a second instead of 10.- Optimizing bundle size is a fun game. We

Hacker NewsToolAISource
0Sign in to voteCopy link

FL score

72

out of 100

Verdict

VALIDATE

high confidence

Competition

No competitor data yet

Trend

No signal yet

Browser-based PCB design tool that ports KiCad to WebAssembly, eliminating installation friction for electronics engineers.

The pain

PCB designers must install heavy desktop software (KiCad, Altium, Eagle) locally. Collaboration is difficult. Access from any machine requires reinstallation. Learning barriers are high for beginners who want to try before committing to installation.

The gap

No mature, feature-complete PCB EDA tool exists in the browser. Existing web tools (EasyEDA, CircuitLab) are simplified and lack KiCad's depth. The technical barrier to porting complex C++ CAD software to WASM has prevented this until now.

Build angle

The team has solved the hard technical problems (WebGL rendering, multithreading via Pthreads, Asyncify with exceptions). They have working code. The next phase is validating whether users actually want this enough to pay, and whether the browser environment can handle real production workflows (large boards, complex designs, performance under load).

Strengths

  • Technical execution is genuinely difficult and they've solved real problems (Binaryen pass for Asyncify+exceptions, WebGL GAL implementation). This creates defensibility.
  • KiCad is open-source and widely trusted by professionals. Porting it preserves credibility versus building from scratch.
  • Removes installation friction, immediate value for trying, learning, and quick edits.
  • Team has deep expertise in CRDT/collaborative editing, which is a natural next feature for PCB design.
  • MVP exists and works across browsers. Not vaporware.

Risks

  • Market validation is unclear. Do PCB designers actually want browser-based tools, or do they prefer native performance and offline access? EasyEDA exists but hasn't captured the professional market.
  • Performance ceiling unknown. Complex boards with thousands of components may hit browser limitations. Real-time DRC and 3D rendering at scale are unproven.
  • Monetization path is undefined. KiCad is free and open-source. Why would users pay? Collaboration features? Cloud storage? Unclear if this justifies a business.
  • Maintenance burden is high. Keeping a WASM port of KiCad in sync with upstream releases is ongoing work. One breaking change in KiCad could require significant rework.
  • Browser compatibility issues remain (Safari is 'working'). Professional users need reliability.
  • No evidence of user demand yet. This is a solution looking for a problem at scale.

Questions about this idea?

FlyBot reads the scoring and gives you a second opinion on “KiCad in the Browser”.

Open FlyBot