Import

LTspice online: open an .asc schematic in the browser and run it

Looking for LTspice online?

Import your own projectEvery tool Mokxi imports from
The box

Drop it here, or paste it

Drop an .asc file here and your browser redraws the schematic as a running Mokxi circuit: resistors, capacitors, diodes, transistors, sources and op-amps where LTspice placed them, the nets worked out from the wires and flags, and a scope ready for any node. Nothing is installed, and the file is read in this tab.

A 5 V source, a 1 kΩ resistor and an LED, with a .tran 5m command and a two-line comment. It opens with two grounds, a red LED, the comment as a sticky note and the transient described in the report.

Paste from ChatGPT or ClaudeCopy a prompt, say what to build, paste the answer.
  1. 1Copy the promptIt teaches your AI how to write a Mokxi project.
  2. 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".
  3. 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.
  1. 1Export the circuitIn Tinkercad, open the circuit, press Export and download the .brd file. It has every part and wire.
  2. 2Download the codeOpen Code, switch to Text and press the download button for the .ino.
  3. 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.
Files and links

What Mokxi reads from LTspice

An .asc schematic as LTspice saves it. Files written as UTF-16 by LTspice XVII and LTspice 24 are decoded before they are read.

The same text pasted into the box, starting with its Version 4 line.

An .asc inside a zip or folder, dropped with whatever else came along with it.

Not a symbol file (.asy): Mokxi refuses one and says it is a symbol, since it holds a drawing and pins rather than a circuit.

Not a netlist (.net or .cir): those are SPICE decks, which the editor opens from Save, then Open JSON or SPICE.

Converted

What comes across

Nets, worked out the way LTspice works them out

An .asc stores coordinates, not connections, so Mokxi joins exactly what LTspice would: a pin, a wire end or a flag standing on one point is one node, a wire ending on the middle of another makes a T junction, two wires that merely cross stay apart, and every flag with the same name belongs to one net. Each flag named 0 becomes a ground part.

The standard symbols, with their pins on file

Sixteen symbols from the stock library have their pin positions copied here from their .asy files: res, res2, cap, polcap, ind, ind2, diode, schottky, zener, led, voltage, current, npn, pnp, nmos and pmos, plus the five-pin op-amps opamp2 and UniversalOpamp2. All but the current source become the Mokxi part of that kind, turned or mirrored as the symbol was.

Model names, when Mokxi has the part

A value such as 2N3904, 1N4007 or IRLZ44N stays on the part when Mokxi has that exact model. When it does not, the part is the default of its kind (the 2N2222 for an NPN, the 1N4148 for a diode, the 2N7000 for an N-channel MOSFET) and the report names the model that was replaced. An LTspice LED symbol carries no color, so it comes in red unless its value says otherwise.

Parameters, comments and the simulation commands

A .param line fills in any {name} used in a value. Comment text (the lines LTspice marks with a semicolon) becomes a sticky note on the canvas. Each directive is described in the report rather than run: a .tran says how long LTspice simulated, a .op that it solved the operating point, and both end by telling you to press Run and read the nodes with a scope or a meter.

Left out

What does not, and what happens instead

Sweeps and parameter steps

An .ac, .dc or .step line is listed as not carried: Mokxi has no frequency or parameter sweep, so the circuit runs in the time domain and a stepped parameter keeps its first value. Turn a source by hand while it runs to see the same effect.

Model cards and libraries

.model, .lib, .include and .subckt lines are not imported; the report says so and that parts use Mokxi's own models. SPICE settings typed onto a part (its SpiceLine) are left out and quoted in the report, as are a source's AC settings.

Current, behavioral and PWL sources

A current source has pin positions on file but no Mokxi part, so it stands as a pink note. So does a voltage source whose value is PWL, EXP or a formula; the report quotes the value and says that Mokxi takes DC, sine and pulse. A SINE or PULSE source whose minus pin is not on ground is a note too, because a Mokxi signal generator is measured from ground.

Every symbol outside the table

ICs, switches, transmission lines, subcircuits and anything else not in the standard set become a note naming the symbol, because their pin positions live in .asy files the schematic does not carry, and pins are never guessed. An op-amp whose V- pin is not on ground is listed the same way: Mokxi's op-amp runs between its supply and ground.

A schematic without a ground flag

When no flag named 0 is in the file, the report says the schematic has no ground and that Mokxi needs one, and asks you to add a ground part where the circuit's 0 V is.

Step by step

From LTspice to Mokxi

  1. Step 1

    In LTspice, save the schematic. The .asc is the file to bring; a .net netlist or an .asy symbol is not.

  2. Step 2

    Drop the .asc into the box above, drag it onto the editor canvas, or paste its text; the hint "Looks like an LTspice schematic" appears once the first lines are recognized.

  3. Step 3

    The editor opens with the circuit drawn and the summary chip listing what came across, what became a note, and what each directive asked LTspice to do.

  4. Step 4

    Press Run and put a scope or meter on the node you were plotting in LTspice. Press T to route the straight pin-to-pin wires around the parts.

FAQ

Questions about importing from LTspice

Can I run LTspice in a browser?

Not LTspice itself: it is a desktop program for Windows and macOS. What you can do is bring its schematic here. Mokxi reads the .asc, rebuilds the circuit from the standard symbols and simulates it in the tab with its own engine, so what you get is a live circuit to probe rather than an LTspice plot.

Which LTspice symbols come across?

The stock ones whose pins are on file: res, res2, cap, polcap, ind, ind2, diode, schottky, zener, led, voltage, npn, pnp, nmos, pmos, and the opamp2 and UniversalOpamp2 op-amps. A model name on one of them is kept when Mokxi has the exact part. Anything else is named in a note at the spot where it stood.

Why is my op-amp a note instead of a part?

Mokxi's op-amp has a positive supply pin and a ground pin, so an LTspice op-amp whose V- pin sits on a negative rail has no direct match and is listed instead. Place a Mokxi op-amp by hand and set its negative rail in its settings, or redraw the stage for a single supply.

What happens to my .tran, .ac and .step commands?

They are read and described in the import report, never executed. A .tran tells you how long LTspice ran; Mokxi runs continuously, so you press Run and watch. An .ac or .dc sweep and a .step are listed as not carried, and the circuit holds the first stepped value.

Can I open an LTspice netlist instead of the schematic?

Yes, through a different door. A .net from View, SPICE Netlist, or any .cir, is a SPICE deck, and the editor opens those from Save, then Open JSON or SPICE. This page reads only the .asc.

Is the .asc sent to a server?

No. The schematic is parsed in your browser, and the importer fetches nothing and runs nothing from the file. What you save afterwards is a Mokxi project, which you can also export as a Wokwi project or an Arduino sketch folder.

Keep going

Where to next

Simulate your circuit in minutes. Build it for real with Pro.

Start free