Simulate an EasyEDA schematic from its EasyEDA Source JSON
Export EasyEDA Source from the EasyEDA Standard editor, drop the .json here, and the schematic simulation starts in your browser.
Drop it here, or paste it
Each part by its designator, value and package, the wires and junctions, the net labels and the power and ground flags, joined into nets as the editor draws them. The circuit runs with an Arduino sketch you add. EasyEDA Pro .epro files and project links are not read.
An Arduino Nano, an LED and a resistor, exported as EasyEDA Source from the Standard editor. It opens wired, with the Nano ready for a sketch.
Paste from ChatGPT or ClaudeCopy a prompt, say what to build, paste the answer.
- 1Copy the promptIt teaches your AI how to write a Mokxi project.
- 2Say what to buildPaste the prompt into ChatGPT, Claude, Gemini or Cursor and add what you want, like "a night light with a light sensor".
- 3Paste its answer hereThe whole reply is fine. It opens wired and ready to run.
Only have a photo or a screenshot of the circuit? Give your AI the picture with this prompt instead.
Your AI app supports MCP? Add the Mokxi server and it builds the link for you. How
From Tinkercad? Three stepsBring a circuit across wired, with its code.
- 1Export the circuitIn Tinkercad, open the circuit, press Export and download the .brd file. It has every part and wire.
- 2Download the codeOpen Code, switch to Text and press the download button for the .ino.
- 3Drop both hereChoose or drop the .brd and the .ino together: it opens wired, with the code on the board. No .brd? Paste the Component List with the code under it.
What Mokxi reads from EasyEDA
The .json written by File, Export, EasyEDA Source in the Standard editor: JSON with editorVersion and docType, whose schematics hold shape strings (LIB~, W~, J~, N~, F~) with ~ between the fields.
The same text pasted into the box.
A zip or folder with the .json and an .ino beside it, for the code.
Files up to 1 MB each. A larger source file is skipped, so export the schematic on its own from a big project.
What comes across
Parts, by designator and package
Each LIB~ shape gives a part its designator (U1, R1), value, package (ARDUINO-NANO, R0603) and pins, and the schematic table shared with the KiCad and EAGLE readers matches resistors, capacitors, inductors, LEDs, diodes, transistors, switches, pots, 74xx and CD4000 chips, common modules and Arduino boards. A part turned in the editor may be stored turned or as drawn plus a turn; both are tried and the one whose pins land on wires is kept.
Nets from the geometry
A source file has no netlist. Each W~ wire’s points form one conductor; a pin end, a J~ junction, an N~ label or an F~ flag that sits on a wire is on that conductor; and labels or flags sharing a name are one net on every sheet, which the report mentions when more than one sheet was read.
Several sheets
The sheets of a project are laid out side by side on the canvas, and parts that would cover each other are nudged apart, with the count in the report.
Code beside it
Drop the .ino with the .json and it is placed on the Arduino in the schematic. When the sheet has no board at all, a note says the code has nowhere to run until you add one.
What does not, and what happens instead
EasyEDA Pro and .epro
A project saved by EasyEDA Pro is a different format that Mokxi does not read yet, and the refusal says so. Only the Standard editor’s source export is read.
Links to easyeda.com and oshwlab.com
A link to easyeda.com, oshwlab.com, lceda.cn or oshwhub.com is recognized and not downloaded; Mokxi answers with the export steps instead.
The PCB, drawings and libraries
A project export that also holds boards gets the note "only the schematic is read". Text and drawings on the sheet, a frame or logo with no pins, and part libraries are left off.
Pins with no match, parts with no row
A pin Mokxi’s part does not have is listed in the report and left unconnected, never guessed. A part absent from the table becomes a pink note naming its designator and value, with the connections it took.
A schematic with no wires
If the file holds parts but no W~ wires, the report notes that nothing is connected. A very large file is cut at its first parts and part of its wiring, and the report says that too.
From EasyEDA to Mokxi
Step 1
In the EasyEDA Standard editor, open the schematic.
Step 2
Choose File, then Export, then EasyEDA Source, and save the .json.
Step 3
Drop the .json in the box above, with the Arduino .ino if there is one; "Looks like an EasyEDA schematic" shows under the box.
Step 4
The editor opens on the circuit and the report: parts mapped, pins left out, sheets read. Tidy the wires with T, add a board if the sheet had none, and run.
Questions about importing from EasyEDA
Can I simulate an EasyEDA circuit without leaving the browser?
Yes. Export the schematic as EasyEDA Source, drop the .json here, and it opens as a live circuit in this tab with the parts and nets the file describes. Put a sketch on the board and press Run.
Which EasyEDA export does Mokxi read?
Only EasyEDA Source from the Standard editor, the JSON whose documents are lists of shape strings. Gerber, PDF, SVG and BOM exports are not read, and neither is an EasyEDA Pro project.
Why not just paste my EasyEDA or OSHWLab link?
Mokxi does not download projects from those sites. The box recognizes the link and tells you the export steps, so the file you drop is one you made yourself.
How does Mokxi know what connects to what if the file has no netlist?
It reads the drawing the way the editor does: every point along a wire is one conductor, and a pin end, junction, label or flag lying on it joins it. Labels and flags with the same name are joined across sheets.
What happens to the PCB in my project?
It is ignored, and the report says only the schematic was read. The circuit on the canvas comes from the schematic documents alone.
Where to next
What this page says about EasyEDA was checked in November 2026 against EasyEDA documentation.
