DocsOpen the editorEditor
Import

Bring your project to Mokxi

From Wokwi, Fritzing, SimulIDE, Falstad CircuitJS, Tinkercad, PlatformIO or the Arduino IDE. Paste a link or some text, or drop a file, a folder or a zip: Mokxi works out which tool it came from, brings the circuit, the code and the libraries list across, and a report says what did not.

or

Drop a project here: a Wokwi project or its zip, a Fritzing .fzz, a SimulIDE .sim1 or .simu, a PlatformIO folder or zip, a CircuitJS text export, a Tinkercad component list (.csv), or an Arduino sketch, sketch folder or zip.

What comes across

  • Import your Wokwi project Paste a public project link, or drop diagram.json with the sketch, or the project zip. A public link is fetched from wokwi.com by our server, which fetches nothing else. Boards, LEDs, resistors, buttons, servos, LCDs, OLEDs, NeoPixels, sensors, keypads and shift registers map to the matching Mokxi part, with their values and pins, and a part plugged into a Wokwi breadboard lands in the same holes.
  • Import your Fritzing project Drop the .fzz. The breadboard view comes across: the core parts (Arduino Uno, Nano and Mega, resistors, LEDs, buttons, pots, sensors, the 555, the 74HC595 and more) where they stood, every wire, and the code from the Code tab. Breadboard strips become wires that join the same pins. The schematic and PCB views are not read.
  • Import your SimulIDE circuit Drop the .sim1 or .simu file, with the sketch beside it. Components, positions, wires, nodes and tunnels come across. SimulIDE loads a compiled .hex, which Mokxi cannot run, so the .ino is what brings the code.
  • Import your Falstad CircuitJS circuit Paste a CircuitJS link (the circuit is inside the link, so nothing is fetched) or the text from Export As Text. Resistors, capacitors, inductors, sources, diodes, LEDs, transistors, MOSFETs, op-amps, pots, switches, the 555 and logic gates become Mokxi parts; anything else becomes a labeled note.
  • Import your PlatformIO project Drop the folder or a zip with platformio.ini. The board comes from the default environment, src/main.cpp becomes the sketch, lib_deps are checked against the libraries Mokxi builds with, and lib/ comes along as the project’s own libraries.
  • Import your Arduino IDE sketch Drop an .ino, a sketch folder or a zip, or paste the code. Mokxi guesses the board from the includes and the pins the sketch uses, you pick from the list, and the project starts with that board on the canvas for you to wire.
  • What does not come across A part Mokxi does not have yet becomes a labeled note on the canvas, and its connections are listed. Every report names each part, connection, file and library it could not bring, with the reason.
  • Your own libraries A libraries folder in the zip (or a PlatformIO lib folder) comes across as the project’s own libraries on Pro. On the Free plan the report names them and the sketch opens without them.
  • Safety Nothing you import is run while it is read. Zips and pasted text are size capped, paths that climb out of the project are refused and named, XML that declares entities is refused, and only source and project files are kept.

Import your Tinkercad project

Tinkercad Circuits keeps projects on its own servers and has no file that says how a circuit is wired, so a Tinkercad project cannot come across whole. These three steps bring over everything Tinkercad lets you take. Mokxi never reads Tinkercad’s pages.

  1. In Tinkercad, open the project, open Code, switch to Text, then select all of the code and copy it.
  2. Open the Component List view and copy the table, or download it as CSV.
  3. Paste the list and then the code into the box above, or drop the .csv and the .ino together. The parts Mokxi has are placed in rows with their values, the code goes on the Uno, and you wire the parts the way your Tinkercad circuit has them.

Taking a project out again

Nothing locks a project in. The editor’s Export menu downloads it as a Wokwi project (diagram.json, sketch.ino and libraries.txt), an Arduino IDE sketch folder, or a PlatformIO project, each as a zip with a README that says what changed on the way.

Importing projects, in the docs · Mokxi and Wokwi, compared · Mokxi and Tinkercad