Export a Tinkercad circuit and open its .brd file with the code
Tinkercad Circuits can export a .brd board file, and its Code panel can export the Arduino code as an .ino.
Drop it here, or paste it
Drop both here and the circuit opens wired, the parts where they stood and the sketch on the board. No .brd? Paste the Component List with the code and the parts arrive in rows. A Tinkercad link cannot be opened, because projects sit behind a sign-in.
A real Tinkercad .brd: an Uno, a photoresistor, LEDs, a piezo, a button and a servo. It opens wired; the export has no code in it, so add a sketch to the board to run it.
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 Tinkercad Circuits
The .brd file from Tinkercad’s Export button: an EAGLE board whose single library is named "Tinkercad". It is recognized by that library, whatever the file is called (.brd, .xml or .txt).
The .ino from the Code panel in Text mode, dropped together with the .brd so the program lands on the board.
The Component List, downloaded as CSV or copied from the page (copied, it arrives tab separated), with the code pasted under it.
A zip or a folder that holds the .brd and the .ino side by side.
What comes across
The parts, by Tinkercad package name
Each <element> in the board is matched by its package (ARDUINO-UNO-R3-SHIELD, RESAD1016W63L850D250B for a resistor, HC-SR04, SG90) through a table written for Tinkercad’s library: the Uno and the micro:bit, LEDs with their color, RGB LEDs, resistors and pots with their value, pushbuttons, slide and DIP switches, piezos, servos, DC and gear motors, the TMP36, photoresistors, the HC-SR04, PIR and IR receiver, soil, force and gas sensors, the 4x4 keypad, 16x2 LCDs plain and I2C, seven-segment displays, NeoPixels, transistors, diodes, capacitors, the 9 V battery and the power supply, relays, the 7805, the L293D, the LM741, the 555, 74HC logic and the CD4511.
The wiring, from the board’s signals
Every <signal> lists the pads it joins and becomes one net, drawn as wires from pin to pin between the parts in it. The breadboard is absent from Tinkercad’s export because its strips were already folded into the signals, so no connection is lost; the report notes that wires which went through it are drawn straight, part to part.
The code, when the .ino is beside it
The sketch goes on the Uno or the micro:bit and compiles in the tab. With the two files together, the report drops its reminder that the board export carries no code.
Settings read from the pads
An I2C LCD’s address is read from its backpack’s A0 to A2 pads, and the report reminds you that Tinkercad’s is often 0x20. Closed solder jumpers join their two sides. The Component List, by contrast, gives values alone: resistor and pot ohms, capacitor microfarads, LED color, battery kind, NeoPixel count and ring or strip layout.
What does not, and what happens instead
A Tinkercad link
tinkercad.com/things/<id> and /embed/<id> are recognized and refused: the project is behind a sign-in Mokxi never has, and Mokxi never reads Tinkercad’s pages. Typed after mokxi.com/, such a link lands on /import#tinkercad, where the three steps are.
Wiring, from the Component List
The list is rows of Name, Quantity and Component and nothing more, so its parts are placed in rows unwired and the summary reads "N parts from the Tinkercad component list, not wired". A row the table does not know is counted as a component with no Mokxi part.
Headers, crystals and the PING sensor
Pin headers (the 1X06 package), jacks and test points are where cables plug in, so they are dropped and named in the report, which asks you to wire whatever met them straight to the parts. A crystal is dropped because the Uno here keeps its own clock. The Parallax PING ultrasonic sensor has no Mokxi part and becomes a note naming it.
Settings the export leaves out
The .brd carries no code, no power supply voltage (set to 5 V here) and no NeoPixel count (set it in the strip’s settings). Tinkercad’s gas sensor is a bare sensor while Mokxi’s is the module with its load resistor, its output on AO; the report says so when one is present.
From Tinkercad Circuits to Mokxi
Step 1
In Tinkercad Circuits, open the circuit, press Export and download the .brd.
Step 2
Open Code, switch to Text, and press the download button to save the .ino (or select all of it and copy).
Step 3
Drop the .brd and the .ino into the box above together. Until the code is there, the box’s own hint is "Looks like a Tinkercad circuit export: add its code (.ino) too, and it opens with both".
Step 4
Without a .brd, open the Component List, download the CSV or copy the table, paste it into the box with the code under it, and wire the rows in the editor.
Questions about importing from Tinkercad Circuits
How do I convert a Tinkercad circuit to Arduino code?
Tinkercad’s Code panel does the conversion: switch it from Blocks to Text and the generated C++ appears, with a download button for the .ino. That file is an ordinary Arduino sketch, so drop it here with the .brd and it compiles against the wired circuit.
Can I open a Tinkercad .brd file without EAGLE?
Yes. The .brd is an EAGLE board XML, and Mokxi reads it in the browser, matching each package name to a part and each signal to wires. You see the circuit live rather than a board layout.
Why can I not paste my Tinkercad link?
Tinkercad keeps projects behind a sign-in, and Mokxi’s server sends none, so the link cannot be fetched. The import box recognizes the link and answers with the export steps instead of failing silently.
What if the export has no wires in it?
Then the report says Tinkercad wrote the parts but no connections between them. The parts are still placed with their values, and you can wire them in the editor, or paste the Component List and wire from that.
Does the breadboard come across?
No, because Tinkercad leaves it out of the .brd; the strips are already part of the signals. The wires arrive straight from pin to pin, and Tidy wires (T) routes them around the parts.
Where to next
What this page says about Tinkercad Circuits was checked in November 2026 against Tinkercad Circuits.
