PixelOkay
Traffic Flow SimulatorEngineering tools / Interactive modeling
● Browser-local
Tools
TRAFFIC ENGINEERING WORKSPACE v2.0

Traffic Flow Simulator

Model junctions, simulate signals and watch queues form or dissolve — all in your browser.

From plan to pulseA simplified traffic model for learning and what-if exploration, not road-safety certification.
ON THE NETWORK0vehicles
TRIPS COMPLETED0since reset
MEAN VEHICLE SPEED0.0km/h
QUEUE LENGTH0vehicles near junctions
AVG. TRIP TIME—seconds · completed trips
LIVE NETWORK

Downtown crossing

● PAUSED100%
CONGESTION Flowing Busy Queued
Click to inspect · drag an intersection · choose a tool to add roads
5 junctions · 4 directed roads
Waiting for your first run.
◉

Shape the network

Add traffic lights and source or destination nodes, connect roads, and set lanes or speed limits in the inspector.

↗

Watch vehicles respond

Signals alternate by approach; routes and safe lane spacing influence how vehicles move and form queues.

▤

Compare scenarios

Pin a baseline, edit your road or signal plan, and compare seeded runs in the Scenario Lab.

Traffic Flow Simulator guide

Build: Pause the simulation, choose a node tool, then click empty map space to place an intersection. Choose Draw road and click a starting node followed by the destination. Select any road or node to adjust settings on the right.

Run: Select traffic demand (vehicles arriving per simulated minute), then run, pause, advance one second or reset. A seeded arrival process creates repeatable scenarios. Vehicles route to reachable sinks, queue at closed signals, and keep spacing on individual lanes.

Signals: North/south traffic runs during the first portion of each cycle, followed by east/west traffic. Amber portions stop arrivals. An intersection's offset changes its signal timing. Road direction and source/sink roles matter.

Scenario Lab: Open the Scenario Lab tab and pin a baseline. Edit your road network, then compare runs for the same simulated time. The signal explorer tests a small set of green splits and offsets; apply a result only if you understand the simplified assumptions. Export the numeric comparison as CSV. The Cancel button stops further study steps.

Evidence limits: This is a simplified educational, one-directional link simulation with idealized traffic behavior. It is not calibrated for engineering-grade traffic capacity, turning conflicts, pedestrian phases, emissions, or travel-time forecasting.

Privacy: Files are read in your browser only. Save the project JSON to retain editable roads and signal settings. Project imports reject malformed networks without altering your current work.

Using Traffic Flow Simulator

Build a simplified directed road network, place sources, destinations, and signals, and compare seeded traffic scenarios or fixed signal plans.

Workflow

  1. Load a sample road network or create a blank network, then draw roads and add sources, destinations, and signals.
  2. Set arrival demand and run the deterministic moving-vehicle simulation; review queues, waits, speeds, and road congestion.
  3. Save a baseline and compare a changed network or fixed signal plan using the scenario lab, then export metrics or a network illustration.

Worked example

Load the downtown crossing sample, keep its demand and seed, and run a baseline. Save it, adjust one signal split, and compare the resulting simulated queues and trip metrics under the same deterministic model.

Limits and data handling

This is a simplified deterministic traffic model, not a real traffic feed, road forecast, safety analysis, or certified signal-setting recommendation. It simplifies junction conflicts, lanes, and driver behavior. Scenario metrics describe simulated vehicles and the selected network; they do not predict field performance.

Frequently asked questions

Does the simulator use live traffic data?

No. It uses the network and demand assumptions in the workspace and runs a simplified simulation; it does not connect to live traffic feeds.

Can the signal explorer recommend certified field timings?

No. It compares fixed timing plans using simplified deterministic runs and cannot recommend certified real-world settings.

Related tools