Install details: files, engines, browser
The steps to install are in Install and start. This chapter is the detail: what goes where, where BetterSPICE looks for ngspice and PSpice, and how the desktop app and the browser version differ.
57.1What the installer puts where
| Location | What it holds |
|---|---|
| Install folder | betterspice.exe, bspice.exe (the command line), ngspice.dll and its code models (vendor\ngspice\bin), the examples folder and the model catalogue (the list of models). The vendor model files themselves aren't installed: Simulate finds them in a folder with the model library (Where the models come from). |
%APPDATA%\BetterSPICE\window.json | Window size, position and maximised state. Restored at the next start if the monitor is still there. |
%APPDATA%\BetterSPICE\recent.json | The last 10 circuits you opened or saved. File shows 8 of them. |
%APPDATA%\BetterSPICE\parts\ | My parts: the .bspart and .bssym files you made or added. |
%APPDATA%\BetterSPICE\agent-token | The key an AI agent needs to reach the running app (Working with an AI agent). |
%APPDATA%\BetterSPICE\betterspice.log | Problems the app can't show anywhere else, and start-up timings. It restarts at 1 MB and keeps the previous one as .old. shows the folder. |
57.2ngspice for vendor models
Simulate runs circuits with vendor subcircuit models (op-amps, regulators, current-sense amplifiers, references) in ngspice-47 through ngspice.dll. The installer ships it. BetterSPICE looks for it in this order:
- The folder named by the environment variable
BSPICE_NGSPICE. - Next to
betterspice.exe. - In
vendor\ngspice\binof a source checkout.scripts\fetch-ngspice.ps1downloads it there.
The status bar says ngspice 47 ready when it's found and ngspice not found when it's not. Without ngspice, Simulate still runs circuits made only of built-in parts and discrete vendor models (diodes, transistors) in the BetterSPICE engine. A circuit that needs ngspice stops with a banner, E_NGSPICE_MISSING, and never fails silently.
57.3PSpice for TI
Some Texas Instruments models are encrypted by Cadence and only PSpice can read them. If PSpice for TI is installed (free from ti.com, default folder C:\Cadence\PSpiceTI), Simulate runs those models in PSpice, hidden, and shows the result like any other run. The progress line says Simulating in PSpice (encrypted vendor models). The environment variable BSPICE_PSPICE points to another installation, or turns PSpice off when set to 0. PSpice for encrypted models explains the limits.
57.4The browser version
The same interface runs in a current Chrome or Edge. Files open through the browser's file picker and save as downloads. Your own parts are kept in the browser's storage (IndexedDB). Simulate and the analyses run the BetterSPICE engine compiled to WebAssembly, in a pool of background workers. The browser version can't run ngspice or PSpice.
57.5The command line
bspice.exe runs the same engine without a window: check circuits, run analyses into CSV, render pictures, build reports, import boards and verify against ngspice. It's installed next to the app. The command line (bspice) lists every command and option.
57.6Desktop or browser
| Feature | Desktop | Browser |
|---|---|---|
| Editor, live simulation, scopes, logic analyzer, inspector, library, model dialog, Part Wizard, symbol editor, examples, import, export image and netlist | Yes | Yes |
| Native Open and Save dialogs, Save as remembering the folder | Yes | File picker and downloads |
| Recent files, file associations, one window for every file opened from Explorer | Yes | No |
| Reload when the open file changes on disk | Yes | No |
| Window size and position remembered, Save / Don't save / Cancel on close | Yes | The browser's "Leave site?" prompt |
| ngspice for vendor models, PSpice for encrypted models | Yes | No, built-in engine only |
| Report | Native, with every analysis | Built in the page: schematic, parts, operating point, waveforms, diagnostics |
| AI agents | Built in, port 47800 | Through bspice serve on the same computer |
| Pop-out windows for scopes, the dock and the Analysis view | Yes | Yes, if pop-ups are allowed |
| My parts storage | %APPDATA%\BetterSPICE\parts | Browser storage |
| Autosave and recovery of unsaved circuits | Yes | Yes |
57.7System requirements
| Requirement | Value |
|---|---|
| Operating system | Windows 10 or 11, 64-bit |
| Memory | 8 GB. Large vendor-model transients in ngspice use more. |
| Display | The window needs at least 1024 x 640. The layout is designed for 1440 x 900 and up, and opens at 1600 x 1000. |
| Fonts | Barlow and JetBrains Mono are loaded from Google Fonts. Offline, the app falls back to the system sans-serif. |
| Browser version | A current Chrome or Edge |