Download Logisim-evolution v4.1.0
Get the stable compiled packages of Logisim-evolution. Free of charge, open-source under GPLv3, and optimized for modern computer science curricula.
Universal Pure Java Cross-Platform Package
Download Universal .JAR File
Works on: Windows, Mac (Intel/M1/M2/M3), and Linux.
*Requires an existing runtime environment deployment of Java 21 or higher. Learn How to Configure Java 21
Looking for native operating system standalone installers? Jump below:
Logisim-evolution for Windows 10 / 11 (x64 & ARM64)
These official Microsoft Windows installer bundles are compiled as standalone .msi packages. They feature an embedded internal Java Runtime Environment (JRE), allowing you to run full hardware simulations instantly without any manual environment variable configuration.
ℹ️ Windows Installation Guideline
- SmartScreen Warning: Because this is an open-source tool without a paid corporate signature, Windows SmartScreen might flag it. Click “More Info” and then “Run Anyway” to proceed.
- Silent Setup Support: Network administrators can deploy this package across campus labs using standard silent execution arguments:
msiexec /i installer.msi /qn. - Project Storage: Ensure saved
.circcircuit files are stored in directory paths without restricted system access privileges.
Logisim-evolution for macOS (Apple Silicon M-Series & Intel Core)
These official Apple macOS packages are distributed as standard standalone .dmg disk images. They contain native runtime wrappers embedded inside, meaning you do not need to install global JDK instances to initialize simulation workloads.
🛑 Bypassing Apple “Damaged File” Error
Because this academic software is an open-source project distributed outside Apple’s commercial App Store ecosystem, macOS Gatekeeper might block execution, falsely claiming the app is “damaged” or from an “unidentified developer”.
How to authorize launch:
- Drag Logisim-evolution into your Applications folder.
- Open Mac System Settings → Privacy & Security.
- Scroll down to the Security tier.
- Locate the notification banner and click “Open Anyway”.
xattr -cr /Applications/Logisim-evolution.app
Logisim-evolution for Linux (Debian, Ubuntu, RHEL & Fedora)
These natively compiled Linux distribution packages are fully integrated with upstream window scaling parameters and accessibility themes. They contain structural launcher configurations that bind seamlessly to standard desktop menus.
💻 Terminal Installation Scripts
Network supervisors or laboratory technicians can run terminal utilities to install the local binary packages silently:
sudo apt update && sudo apt install ./logisim-evolution_4.1.0_amd64.deb
sudo dnf localinstall logisim-evolution-4.1.0-1.x86_64.rpm
How to Configure Java 21 Environment & Execute Portable Universal .JAR
Unlike standalone native OS installers, the universal compilation framework requires a verified Java Runtime Environment (JRE) or Java Development Kit (JDK) 21 or higher. Follow this system deployment architecture to initialize the simulator via command-line terminals.
Windows Environment Paths
- Download the official OpenJDK 21 msi package from Eclipse Temurin or Oracle registries.
- Run the setup, ensuring you toggle the property “Set JAVA_HOME variable” and “Add to PATH” to true.
- Open Windows PowerShell or CMD terminal layout and verify installation by querying:
java -version.
macOS Homebrew Toolchain
- For Apple computers, initializing via Homebrew package manager parameters is highly optimal.
- Launch standard macOS Terminal shell layout and execute terminal directive command:
brew install openjdk@21 - Bind runtime system linking references directly inside your local profile shell scripts (
.zshrc).
Linux Native Package Manager
- Linux workstation clusters sync native JRE libraries directly using core maintainer packages.
- For Ubuntu/Debian terminals:
sudo apt install openjdk-21-jre - For RedHat/Fedora workstations:
sudo dnf install java-21-openjdk
🚀 Launching Logisim-evolution via CLI Console
Once Java 21 variable layers are verified, open your native system command terminal utility, navigate precisely to the specific directory where the logisim-evolution-4.1.0-all.jar file was stored, and run the execution handle command:
java -jar logisim-evolution-4.1.0-all.jar
❌ Troubleshooting Core Runtime Java Errors:
Error: “UnsupportedClassVersionError” (Class file version 65.0)
This issue indicates that Logisim-evolution is trying to load but detects an obsolete legacy environment variable (like Java 8 or Java 11). System parameters require version 21+ compilation headers to synchronize dependencies properly. Run java -version locally to guarantee path references are correct.
Version Migration Guide & Legacy .CIRC File Compatibility
📂 Importing Older Logisim Layout Templates
Logisim-evolution (v4.1.0) utilizes an advanced, refactored XML layout serialization layout to store graphical gate alignments. If you are migrating academic assets created in legacy upstream forks (such as Carl Burch’s original 2.7.1 distribution or the intermediate Holy Cross packages), please review these operational boundaries:
- Automated XML Upscaling: Standard gate representations, wire paths, and custom sub-circuit blocks are automatically parsed and translated into modern evolution formats upon initialization.
- One-Way Conversion Rule: Once a legacy
.circschematic sheet is saved inside the modern evolution engine, its metadata tree structure can no longer be loaded into older 2.7.x binaries. Always duplicate your student project templates prior to opening them. - Deprecated Component Exceptions: Highly custom legacy layout components that lack formal definitions under modern VHDL compile rules may require manual reconnection.
🧹 Clean Uninstallation & Purging Guide
If an existing broken installation script blocks the setup wizard initialization, or if execution paths remain locked, you must completely purge legacy runtime directories from system variables profiles:
Remove-Item -Recycle -Force "$env:USERPROFILE\.logisim-evolution"
rm -rf ~/Library/Application\ Support/logisim-evolution
Installation Troubleshooting & Deployment FAQ
Resolve runtime configuration exceptions, operating framework deployment loops, and administrative directory execution blocks.
Q: Why does the Windows .MSI standalone installer trigger a rollback loop or fail to complete execution lines?
This manifestation typically occurs if an active anti-virus suite flags the background execution properties of the embedded runtime compilation layer, or if residual registry keys from older legacy logisim branches cause structural configuration collisions. To bypass this parameters block, explicitly launch the installer package with elevated administrator privileges, temporarily toggle restrictive third-party security layers off, or use the universal compiled portable jar file format.
Q: Why do Windows SmartScreen and Windows Defender flag the download package as an unrecognized threat?
Logisim-evolution is completely safe, transparent, open-source software built under strict GPLv3 verification. However, because it is an academic project maintained by educational institutions rather than a commercial product, the developers do not purchase expensive corporate code-signing certificates from Microsoft or Apple. To proceed with execution on Windows, click “More Info” inside the SmartScreen pop-up modal and select “Run Anyway”.
Q: Why does the simulator drop access exceptions when trying to read or execute saved .circ canvas layouts?
This behavior indicates a directory workspace privilege block rather than a structural bug inside the application architecture itself. If you attempt to save or parse complex circuit schemes directly inside systemic root repositories (such as protected laboratory program directories or system folders), the Java background execution container will fail write operations. Ensure your project target path is set to localized directories such as user desktops or dedicated document profiles.