Skip to workspace
PixelOkay
● Private · Runs in browser
Tools
CIRCUIT LAB / INTERACTIVE STUDIO

Digital Logic Simulator

Build a circuit. Change inputs. Watch the logic respond.

Local workspace
Ready
100%
SCHEMATIC VIEW · Scroll canvas to pan
0 components0 wires
DEBUG & ANALYZE

Signal waveform

Binary history over manual input changes and clock steps.

0 samples
PIX ELOKAY · LEARN BY BUILDING

From basic gates to stateful circuits.

Try the half adder, a rising-edge flip-flop, or a four-bit register. All signal calculations are performed on your device.

0 / 1 / XSignal states
4-bitRegister width
256Truth-table rows

Using Digital Logic Simulator

Choose a sample or place components, connect compatible pins and adjust inputs. Recalculate combinational outputs or pulse the clock to explore memory. Inspect waveforms or a supported truth table and download JSON to keep an editable backup.

States are ideal 0, 1 or unknown X, without physical propagation delay or accurate hardware timing. Auto clock playback is approximate; combinational truth tables support at most eight switches. Structural changes clear waveform history, which is not saved in JSON. Browser storage and multi-tab conflict handling are best effort.

Choose an editable circuit, diagram or logic table

Practice: compare two switch inputs

  1. Open a simple combinational example or connect two switches to a supported gate.
  2. Change the inputs and inspect the resulting logical states.
  3. Use a supported truth table, then save JSON before changing the circuit structure.

This is an authored logic exercise, not a propagation-delay test or a hardware waveform capture.

Digital logic questions

Does the waveform show accurate physical gate timing?

No. States are ideal 0, 1 or unknown X, with supported rising-edge updates. Physical propagation delay and accurate real-time hardware timing are not modeled.

Why are a large truth table or old waveforms unavailable?

Combinational truth tables are bounded to eight switches. Structural changes clear waveform history, which is not saved in JSON. Keep supported CSV output separately when you need it.

Related tools