How to Open a Wokwi Project in Mokxi

You built a circuit in Wokwi, and now you want to open it in Mokxi. Maybe a friend shared a link, maybe you want to try the same sketch in a second simulator, or maybe you just like to compare. Either way, importing takes a minute. In this post you will open a small Arduino Uno project (one LED and one button), run it, and learn exactly what the import carries over and what it tells you it left behind.

What you need

A Wokwi project is a few files. The ones Mokxi reads are diagram.json (the parts and wires), your sketch and any extra tabs, libraries.txt if the project has one, and wokwi.toml if it has one. You can paste a public project link, drop the project's zip, or drop the files themselves. A private project cannot be fetched by link, so download its zip from Wokwi and drop that instead.

The fastest route is the address bar: type mokxi.com/ in front of a public project link and press Enter. The editor opens with the project imported. No account is needed for that.

The demo project

I made a tiny project for this post so nothing in it belongs to anyone else. An Uno drives a red LED on pin 10 through a 220 ohm resistor, and a button on pin 2 toggles it.

From	To	Why
Uno pin 10	Resistor, leg 1	Sends the signal to the LED
Resistor, leg 2	LED anode (A)	The resistor limits the current
LED cathode (C)	Uno GND	Completes the circuit
Button, leg 1	Uno pin 2	The pin we read
Button, leg 2	Uno GND	Pressing connects pin 2 to ground

Here is its diagram.json:

{
  "version": 1,
  "author": "Mokxi AI",
  "editor": "wokwi",
  "parts": [
    { "type": "wokwi-arduino-uno", "id": "uno", "top": 0, "left": 0, "attrs": {} },
    { "type": "wokwi-led", "id": "led1", "top": -90, "left": 180, "attrs": { "color": "red" } },
    { "type": "wokwi-resistor", "id": "r1", "top": -40, "left": 120, "attrs": { "value": "220" } },
    { "type": "wokwi-pushbutton", "id": "btn1", "top": -90, "left": 270, "attrs": { "color": "green" } }
  ],
  "connections": [
    [ "uno:10", "r1:1", "green", [ "v-20" ] ],
    [ "r1:2", "led1:A", "green", [ "v0" ] ],
    [ "led1:C", "uno:GND.1", "black", [ "v0" ] ],
    [ "btn1:1.l", "uno:2", "blue", [ "v0" ] ],
    [ "btn1:2.l", "uno:GND.2", "black", [ "v0" ] ]
  ],
  "dependencies": {}
}

And here is the complete sketch:

const int BUTTON_PIN = 2;
const int LED_PIN = 10;

bool ledOn = false;
bool lastReading = HIGH;
unsigned long lastChange = 0;

void setup() {
  pinMode(LED_PIN, OUTPUT);
  pinMode(BUTTON_PIN, INPUT_PULLUP);
  Serial.begin(9600);
  Serial.println("Press the button to toggle the LED");
}

void loop() {
  bool reading = digitalRead(BUTTON_PIN);
  if (reading != lastReading && millis() - lastChange > 30) {
    lastChange = millis();
    lastReading = reading;
    if (reading == LOW) {
      ledOn = !ledOn;
      digitalWrite(LED_PIN, ledOn ? HIGH : LOW);
      Serial.println(ledOn ? "LED on" : "LED off");
    }
  }
}

Bring it in

1. Open the import page, or choose Import a project in the editor's Save menu.
2. Paste the link, or drop diagram.json and sketch.ino together.
3. Read the summary line. Press it to see the full report.

I ran this exact project through Mokxi's importer while writing. All four parts became Mokxi parts (the Uno, the LED, the resistor and the pushbutton) and all five connections were made. The only note said the wires follow the route drawn in Wokwi, and that Tidy wires will route them around the parts.

What carries over

In the project	In Mokxi
Parts and their settings	The matching Mokxi part, with color, value and I2C address kept
Connections	Wires, each keeping its color
Sketch and extra tabs	The board's files in the code panel
libraries.txt	Named in the report; libraries Mokxi ships are already installed
Notes (wokwi-text)	Sticky notes

What the report says did not carry over

The report is the honest part, and it comes with a reason for each item. These are the ones to look for:

• A library Mokxi does not ship. I added a made-up name to libraries.txt to test this. The report marked the real ones as installed and the made-up one as missing, with the next step: search the Arduino Library Manager under the code, or upload it with Add library.
• Custom chips. A custom chip is a compiled program, so it arrives as a note. Build the same logic from parts, or package it as a Mokxi chip.
• MicroPython. Mokxi builds Arduino C++. Python files are kept as text but do not run.
• Starting positions. A knob, slide switch or distance slider starts at rest in Mokxi. The report says where the original started, and you move it on the canvas while the sketch runs.
• Boards that are drawn but not run. Some boards come across with wires and code but Run does not start them yet.
• Settings from wokwi.toml such as port forwarding or a GDB server. Each one is named with what to do instead.

If an import fails or something looks off, use Tell us. It sends where the project came from and what was missing, never your code. Also, Undo on the summary line puts your previous project back.

Walk through the sketch

• Lines 1 and 2 name the two pins, so a wiring change is one edit.
• Lines 4 to 6 hold the state: whether the LED is on, the last button reading, and when it last changed.
• setup() makes pin 10 an output and pin 2 an input with INPUT_PULLUP. A pull-up resistor keeps the pin at a known high level when the button is not pressed, so the button only has to connect it to ground. That means pressed reads LOW.
• loop() reads the button and compares it with the last reading. A real button bounces, flickering for a few milliseconds when pressed, so the millis() - lastChange > 30 check ignores changes that arrive too soon.
• When the reading is LOW (a real press), the sketch flips ledOn, writes it to the LED and prints a line to the serial monitor.

Run it

Press Run, then click the button on the canvas. The LED toggles, and the serial monitor prints "LED on" and "LED off" in turn.

What to try next

• Change LED_PIN to 9, move the wire, and run again.
• Add a second LED on pin 11 that is on when the first is off.
• Import a project you did not write, and read its report line by line.
• Read Coming from Wokwi for what each idea is called here, the switching guide, or the factual side-by-side comparison.

Ready to build it yourself? Create your free Mokxi account and open the editor in your browser. No installs, no parts to buy.