iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
SPICE originally stood for “Simulation Program with Integrated Circuit Emphasis.” The University of California, Berkeley developed it from the earlier CANCER circuit-analysis program, with Donald O. Pederson leading the effort and Laurence W. Nagel serving as the principal developer of the early implementation. The first SPICE version was essentially complete in 1972. Berkeley’s source-available releases then influenced commercial and open-source simulators including PSpice, HSPICE, ngspice, LTspice and QSPICE.
Today, “SPICE” means both the historical Berkeley program and a broad family of circuit simulators. They share concepts such as textual netlists, device models and numerical analyses, but their solvers, syntax, model libraries, interfaces and compatibility are not identical.
Why Berkeley needed a circuit simulator
Integrated circuits put thousands, then millions, of interacting devices onto a small piece of silicon. Manual calculations could explain individual stages, but they became impractical for complete nonlinear circuits. Breadboards also failed to reproduce many integrated-circuit effects, including parasitic elements, device matching, thermal interactions and fabrication-dependent behavior.
Recommended Free Tools
Computer simulation offered a way to estimate circuit performance before fabrication or laboratory construction. Berkeley’s 1976 SPICE2 reference describes simulation as a means of evaluating an IC during design, when physical prototypes were expensive and could not expose every relevant effect. See the SPICE2 program reference.
#1 Best Overall
SPICE did not replace measurement. Its predictions depend on the circuit description, semiconductor models, parameter values, numerical settings and assumptions. A converged waveform is a calculated result, not proof that hardware will behave identically.
From CANCER to the first SPICE
Berkeley’s work began before the SPICE name. Laurence Nagel’s dissertation records that SPICE evolved from CANCER, an earlier Berkeley circuit-analysis program, and that the first SPICE version was essentially complete in 1972. By the time of the dissertation, more than 100 copies had reached universities and industrial companies. The SPICE2 dissertation PDF is the primary historical account.
It is misleading to credit the invention to one person. Pederson led the Berkeley effort; Nagel was the central early implementer and author of the foundational SPICE2 work. Thomas Quarles later became closely associated with SPICE3 documentation and development, while Alberto Sangiovanni-Vincentelli and Richard Newton were important figures in Berkeley’s wider electronic-design-automation research environment.
Berkeley’s retrospective histories describe SPICE development through the 1970s and early 1990s and its influence on academic, industrial and commercial design tools. See the Berkeley Engineering timeline and the Berkeley design-automation history.
What the original SPICE program did
The early program was a text-driven analysis tool, not a modern schematic editor. A user prepared a netlist, often called a SPICE deck, containing components, node connections, values, sources, semiconductor models, analysis commands and requested outputs.
Berkeley’s SPICE family supported a substantial set of analyses:
- DC operating-point and nonlinear DC analysis
- Nonlinear transient analysis
- Small-signal AC analysis
- Noise analysis
- Harmonic-distortion analysis
- DC sensitivity analysis
The 1976 SPICE2 reference documents these analysis types and the device classes available at the time, including passive elements, dependent sources, transmission lines and semiconductor devices.
SPICE2: the major early expansion
SPICE2 was a substantial technical advance rather than a cosmetic revision. Experience with the first release led Berkeley to expand the supported elements and devices, improve nonlinear and transient calculations, and strengthen the way circuit equations were assembled and solved. Nagel’s SPICE2 dissertation page and its full PDF describe the algorithms and performance.
At a high level, SPICE2 used modified nodal analysis to translate a circuit into a matrix equation. It added variable-timestep transient simulation and numerical-integration choices such as trapezoidal and Gear-type methods. Memory-management techniques were designed for the computers of the period. In plain terms, SPICE2 became better at converting a nonlinear circuit into equations that could be solved repeatedly as voltages and currents changed.
How a SPICE simulation works
Although implementations differ, a run generally follows this sequence:
- Read and parse the netlist, models, parameters and analysis commands.
- Create the circuit’s nodes, devices and internal variables.
- Assemble a matrix representation of the circuit equations.
- Solve for an operating point, frequency response or time-domain result.
- Linearize or otherwise approximate nonlinear devices and iterate until the equations are sufficiently consistent.
- Adjust timesteps, damping or continuation methods when convergence is difficult.
- Store voltages, currents, powers and derived quantities for display or further processing.
The ngspice documentation describes this preprocessing, matrix-assembly and solution flow. A diode, transistor or behavioral device does not behave like a fixed resistor, so the simulator repeatedly updates its approximation during a solve.
A minimal netlist illustrates the original text-based workflow:
* Simple RC transient circuit
V1 in 0 PULSE(0 5 0 1n 1n 5m 10m)
R1 in out 1k
C1 out 0 1u
.tran 10u 20m
.endHere, node 0 is ground, the source drives an RC network, and .tran requests a transient analysis. Exact syntax and supported source expressions vary among simulators, so this example should be checked in the chosen implementation.
SPICE3 and the move to C
SPICE3 was a redesign, not simply another small feature release. Berkeley moved the implementation toward C, introduced a more interactive environment and made the simulator easier to extend. Its Nutmeg front end allowed users to control analyses and inspect results interactively.
Berkeley’s SPICE page provides Spice3f manuals and examples. Additional historical and technical material is listed by ngspice literature and the project’s developer documentation.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteSPICE3 and Spice3f.5 refer to Berkeley releases. ngspice is a later open-source continuation and extension, not an unchanged Berkeley executable. Commercial products may have started from Berkeley code, preserved compatibility ideas, or been independently implemented while diverging in their solvers and models.
Why Berkeley’s distribution model mattered
Berkeley made SPICE broadly available with source code. That decision let universities teach circuit simulation without expensive licenses, allowed companies to adapt the software to their hardware and workflows, and gave researchers an implementation they could inspect and modify. A shared netlist and modeling culture emerged.
Not every later simulator is legally or technically a direct fork of Berkeley source. Some descended from Berkeley releases; others were commercial rewrites or independent implementations that retained SPICE-like methods and compatibility. Berkeley Engineering describes the public-domain program’s influence on academic, industrial and commercial tools in its integrated-circuits timeline.
Commercial branches of the SPICE family
PSpice
PSpice became a major PC-oriented and schematic-driven implementation and is now associated with Cadence. Current editions, support terms and product names change, so readers should use Cadence’s official support and product entry point for current information. PSpice illustrates how a SPICE engine can be packaged with graphical capture, libraries, analysis controls and vendor support.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteHSPICE
HSPICE is a commercial simulator associated with Synopsys and widely used in semiconductor and integrated-circuit workflows. Its current licensing and supported environments are enterprise matters; no universal public price should be assumed. It is better understood as a production-oriented branch of transistor-level simulation than as the original Berkeley program.
Spectre and other IC simulators
Modern environments such as Spectre represent the broader evolution of analog and mixed-signal EDA. They should not be described as Berkeley SPICE under another name. Their solvers, device formulations, integration features and foundry workflows can differ substantially.
ngspice and open-source continuation
ngspice is the most prominent open-source continuation in current use. Its documentation, literature and developer pages are available from the project documentation hub. The project incorporates historical Berkeley SPICE3 work and extensions associated with XSPICE and CIDER-related semiconductor simulation.
ngspice can run as a command-line simulator or as a shared library controlled by another program. Its FAQ describes this library-oriented use, which makes it suitable for automation, scripting and integration with open electronic-design tools. KiCad installations and configurations can use different ngspice versions, so compatibility should be checked rather than assumed.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
XSPICE and mixed-signal extensions
XSPICE extended the traditional analog focus with code models and mixed-signal capabilities. The ngspice literature page documents this history. Such extensions allow analog equations to interact with digital or event-driven elements and let users add behavior beyond built-in devices.
“Mixed-signal support” is not a universal feature set. One simulator may provide digital blocks, another Verilog-A, another Verilog or C/C++ models, and another event-driven code models. A design that runs in one environment may require model or syntax changes in another.
LTspice: a vendor-focused modern implementation
LTspice is maintained by Analog Devices after its acquisition of Linear Technology. Analog Devices describes it as a fast, free and unlimited SPICE simulator with schematic capture, waveform viewing and device models. Its official page currently surfaces Windows 10/11 x64 version 26.0.2 and model updates dated July 22, 2026; software details can change, so consult the official LTspice page.
LTspice has its own schematic format, syntax, behavioral features and vendor-oriented examples. Analog Devices warns that some macromodels use proprietary languages native to LTspice and may not run on other SPICE platforms; see its model and compatibility guidance.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →QSPICE and a newer simulator generation
QSPICE, associated with Qorvo and developed around the work of Mike Engelhardt, extends SPICE concepts with analog and mixed-signal simulation, C++ and Verilog support, and a modern schematic and waveform workflow. Qorvo advertises local downloadable execution and free commercial use. Its stated requirements include Windows 10 64-bit or Windows 11, 4 GB of RAM minimum and 16 GB recommended. Details are on the official QSPICE page.
QSPICE is not “the latest version of SPICE.” It is a current vendor implementation with its own features, models, update policy and platform requirements.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What “SPICE-compatible” really means
Compatibility usually means that a simulator recognizes some familiar netlist conventions or analysis commands. It does not guarantee that every model or deck will run unchanged.
- Syntax: behavioral expressions, control statements and device parameters differ.
- Models: semiconductor model levels, defaults and parameter interpretations vary.
- Subcircuits: pin order must match exactly.
- Proprietary languages: encrypted or vendor-specific macromodels may be restricted to one simulator.
- Numerics: tolerances, timestep policies and convergence algorithms can produce different results.
- Libraries: a component model may exist in one vendor library but not another.
Always validate a converted model against its datasheet, operating range and original simulator. A model that runs successfully can still be physically inappropriate.
Why simulations fail or mislead
- Floating nodes or a missing ground leave the equations underdefined.
- Ideal voltage sources can create zero-impedance loops and unrealistic transients.
- Very abrupt switching, poor value scaling or discontinuous behavioral expressions can defeat convergence.
- Oscillators may remain at a perfectly symmetrical equilibrium unless startup noise or an initial condition is provided.
- Incomplete, encrypted or incompatible models can produce errors or misleading defaults.
- Switching regulators require careful timestep, startup, parasitic and control-loop treatment.
- Op-amp macromodels are valid only within their specified supply, load, frequency and common-mode ranges.
- Basic lumped-element SPICE does not automatically include distributed electromagnetic or coupled thermal effects.
Convergence means that the numerical procedure found a solution under the selected assumptions. It does not validate component tolerances, layout parasitics, temperature, aging, measurement loading or manufacturing variation. The practical engineering loop remains design, model, simulate, sensitivity-check, prototype, measure, correlate and refine.
SPICE tools compared by use case
| Need | Suitable options | Main trade-off |
|---|---|---|
| Learn classic netlists and open simulation | ngspice | Usually needs a separate graphical front end for a polished schematic workflow |
| Free schematic-based analog simulation | LTspice | Strong Analog Devices ecosystem, but proprietary models and syntax can limit portability |
| Free mixed-signal work with C++ or Verilog | QSPICE | Officially centered on Windows requirements and a vendor-specific ecosystem |
| Open-source automation or embedded simulation | ngspice library/API | Requires software integration and more technical setup |
| Integrated PCB and schematic workflow | KiCad with a SPICE backend such as ngspice | Front-end behavior and model support depend on the installed configuration |
| Production IC verification and foundry integration | HSPICE, Spectre and other commercial EDA environments | Enterprise licensing, setup complexity and specialized model requirements |
This is an orientation, not a performance ranking. No controlled benchmark establishes one universal winner.
Historical timeline
| Date or period | Development | Qualification |
|---|---|---|
| Late 1960s | Berkeley circuit-simulation research and CANCER | SPICE2 documentation identifies CANCER as its predecessor. |
| 1972 | First SPICE essentially completed | Reported in Nagel’s SPICE2 dissertation. |
| 1975 | SPICE2 documented | Nagel’s dissertation describes its algorithms and performance. |
| 1976 | SPICE2 program reference published | Documents analyses, devices and internal design. |
| 1980s | Commercial and industrial adoption expands | Berkeley histories support broad influence; individual company dates require separate attribution. |
| Late 1980s–early 1990s | SPICE3 and Nutmeg become important Berkeley releases | Berkeley and ngspice documentation describe the C-based interactive environment. |
| 1993 | SPICE3f.5 commonly treated as the last stable Berkeley SPICE3 release | This characterization belongs to later project histories, including ngspice material. |
| 1990s onward | Commercial, academic and open-source descendants proliferate | Documented by Berkeley historical accounts. |
| 2026 | SPICE-derived tools remain active | Current project and vendor pages list ngspice, LTspice and QSPICE offerings. |
The lasting significance of SPICE
SPICE’s achievement was larger than any one executable. Berkeley made numerical circuit simulation practical for complex nonlinear integrated circuits, distributed an implementation that others could study and adapt, and helped establish a shared language of nodes, models, analyses and circuit decks.
That legacy explains both the family resemblance and the differences among modern tools. ngspice preserves an open connection to Berkeley’s SPICE3 tradition; LTspice and QSPICE package SPICE methods with vendor-specific interfaces and extensions; PSpice and HSPICE serve commercial design ecosystems; and enterprise IC simulators integrate simulation with foundry and verification flows. Choosing among them means matching the simulator, models, platform and support requirements to the engineering problem—not assuming that every program carrying the SPICE name is interchangeable.
Free tools Windows power users keep installed
One-click scans. No signup required.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
