OPNsense

Home›Blog›Download & Install›OPNsense Download: Get the Official Installer Image Safely

OPNsense Download: Get the Official Installer Image Safely

Category: Download & Install · Updated 2026-11-19 · Applies to OPNsense 26.7

Illustration of a computer downloading the OPNsense installer image from an official mirror

You can download OPNsense free of charge, directly from this website. The chooser in the download section of our homepage serves the official installer files straight from the OPNsense project release server, so the file you receive is the genuine project release, never a repackaged copy. The current installer image is OPNsense 26.7, for the amd64 architecture (the only option), in four image types: dvd, vga, serial and nano. Choose the type that matches your hardware, click the download button, and you will receive a single bzip2-compressed file such as OPNsense-26.7-vga-amd64.img.bz2. This guide walks through each choice, explains what you actually get, and shows how to confirm that the file on your disk is the genuine, current release before you install it on anything.

What you are downloading

OPNsense is an open source firewall and routing platform based on FreeBSD. The current Community Edition series is 26.7, codenamed "Xenial Xenops", released on 15 July 2026 and based on FreeBSD 15.1. Like every OPNsense series, it receives minor updates roughly every two weeks, and the latest of those is 26.7.9, published on 11 November 2026.

One detail surprises many first-time users: the downloadable image does not chase every minor update. Installer images are only rebuilt for the two major releases each year (January and July), so the image you download today is version 26.7, even though 26.7.9 is the newest update. That is normal and by design. You install from the 26.7 image, then apply the pending updates from the web interface or console once the system is running, which brings you fully up to date. The next scheduled image is 27.1 in January 2027.

There is also a Business Edition of OPNsense. It is a paid, per-installation subscription edition that follows a more selective, slower upgrade path and adds some commercial extras. It is not what the public download page offers. Everything in this guide covers the free Community Edition, which is what almost all home and small network users run.

Before you download: what you need

The download itself is small and quick, but a few minutes of preparation will save you from the most common dead ends.

  • A 64-bit x86 computer to install on. OPNsense is published for the x86-64 architecture only, listed as amd64 on the download page. There are no 32-bit or ARM images, so an old 32-bit PC or a Raspberry Pi cannot run it.
  • A USB flash drive for the installer. Most people install from USB. A basic drive is fine for the installer images, and if you plan to use the preinstalled nano image you need a drive, SD card or CF card of at least 4 GB, because nano itself becomes the running system.
  • Enough RAM in the target machine. The official hardware guide sets the minimum at 3 GB of RAM (the installer itself needs 3 GB to run), with 4 GB described as reasonable and 8 GB as recommended.
  • A second computer for the download. You will download and prepare the image on a working machine, then carry the USB drive to the firewall hardware.

If you are still deciding which hardware to use, settle that first, because the hardware decides one of the download options below: whether the machine has a monitor or only a serial console.

Step 1: Choose the image type

The download chooser on this site offers four image types. They contain the same OPNsense software; they differ in how you connect to the machine during installation and in whether an installer runs at all. Choosing the wrong one is the single most common download mistake, and it usually means a blank screen or a silent console at boot time.

ImageFile you receiveConsoleBest for
dvdOPNsense-26.7-dvd-amd64.iso.bz2Monitor and keyboard (VGA)Burning a DVD, or installing into a virtual machine from an ISO file
vgaOPNsense-26.7-vga-amd64.img.bz2Monitor and keyboard (VGA)The standard choice: a USB installer for a PC, mini PC or server with a display
serialOPNsense-26.7-serial-amd64.img.bz2Serial console only, at 115200 baudHeadless appliances and embedded boards with no display output
nanoOPNsense-26.7-nano-amd64.img.bz2Serial console, with limited secondary VGAA preinstalled system that runs directly from a USB drive, SD or CF card

For a typical home firewall build with a monitor attached, the vga image is the right download. If your hardware has no video output at all and you manage it through a serial cable, you need serial instead, because the vga image shows nothing on a serial console and the serial image shows nothing on a monitor. The nano image is a different concept entirely: it is already installed, so you write it to a card or drive and boot straight into a running system, with no installer step. If you are weighing these options in detail, our comparison of VGA vs DVD vs Serial vs Nano walks through each one against real hardware situations.

Step 2: Download from this site

OPNsense is distributed through a worldwide network of mirror servers run by the project and its partners. The download buttons on this website connect to the project's own release server, which delivers the same files the mirrors carry, so the contents are identical wherever they are served from. The choice of server affects only download speed and reliability, never the contents.

A practical approach:

  1. Go to the download section of our homepage.
  2. Select your image type in the chooser; the architecture is amd64 (it is the only choice).
  3. Check that the filename shown under the button matches the image type you selected, including the .bz2 ending.
  4. Click the download button and save the file somewhere you can find it again, such as your Downloads folder.
  5. Download the SHA256 checksum file from the same section, so you can verify the image before using it.

If a download stalls or arrives suspiciously fast for a file of this size, cancel it and start it again. A partial file will fail verification later, and starting again is faster than troubleshooting a corrupt download.

Understanding the file name

Every official file follows the same naming pattern, OPNsense-<version>-<type>-amd64.<ext>.bz2, and reading it tells you exactly what you have:

  • 26.7 is the release the image was built from.
  • vga, dvd, serial or nano is the image type you selected.
  • amd64 confirms the x86-64 architecture.
  • .iso appears only on the dvd image; the USB-based types use .img.
  • .bz2 means the file is compressed with bzip2 to make the download smaller.

The compression matters for the next step. An image writer that understands .bz2 files can write the download directly; most cannot, so you will usually decompress the file first, turning OPNsense-26.7-vga-amd64.img.bz2 into OPNsense-26.7-vga-amd64.img. On Linux and macOS the bunzip2 command does this, and on Windows a tool such as 7-Zip can extract it. Do not try to copy the .img file onto a USB drive as a normal file: it has to be written as a raw disk image, which is covered step by step in our guide to creating an OPNsense bootable USB drive.

While you are on the mirror, it is worth downloading two small extra files from the same release directory: the checksum list, named OPNsense-26.7-checksums-amd64.sha256, and the matching signature file. They cost seconds and let you prove the image is genuine, as described below.

Why you should only download from official sources

A firewall sits at the edge of your network and sees every packet that enters or leaves it. That position of trust is exactly why the source of the installer matters more for OPNsense than for ordinary software. Unofficial download sites, repacked images in forum posts, and "preinstalled" drives from unknown sellers all carry the same risk: you cannot know whether the code was modified, and a modified firewall can hide its tracks very effectively.

The official channels are the download page at opnsense.org, its listed mirrors, and the release announcements in the official documentation and forum. Stick to those, and then verify what you downloaded. Verification is not paranoia; it also catches ordinary corruption from an interrupted download, which is far more common than tampering and just as capable of ruining an installation.

Step 3: Verify the download before you install

The project publishes a SHA256 checksum for every image. You compute the checksum of your downloaded file and compare it with the published value: if the two long strings of characters match exactly, your file is bit-for-bit identical to the one the project released. The checksum file sits next to the images on every mirror, and each uncompressed image also has an OpenSSL signature file, so you can go further and check the project's digital signature as well, which ends with the reassuring output "Verified OK".

One caution comes straight from the project: a checksum file downloaded from the same mirror as the image cannot by itself prove authenticity, because a compromised mirror could replace both. For real confidence, cross-check the checksum or the signing key against a second official source, such as the release notes, the forum announcement or the GitHub changelog. Our dedicated guide, How to Verify Your OPNsense Download with SHA256 and OpenSSL, gives the exact commands for Windows, macOS and Linux and explains both checks in full.

How to confirm you have the right download

Before moving on, run through this short confirmation list. If every point holds, your download is correct and complete:

  • The file came from opnsense.org/download or a mirror listed there.
  • The file name contains 26.7 and amd64, and the type (dvd, vga, serial or nano) matches your hardware and console.
  • The download finished completely, with no browser error or resume prompt.
  • The SHA256 checksum of your file matches the value in OPNsense-26.7-checksums-amd64.sha256.
  • You know the next step for your image type: write it to USB (or a card for nano), then install.

Common download mistakes

Downloading an image for the wrong console

A vga image on a headless box, or a serial image on a machine with a monitor, boots into silence. The fix is simply to download the matching type; the comparison in VGA vs DVD vs Serial vs Nano explains how to tell which console your hardware really uses.

Expecting an ARM or 32-bit build

There is none. OPNsense setup is available for x86-64 only, so hardware that cannot run 64-bit x86 code needs to be replaced or used for something else.

Grabbing an old release from a third-party site

Software archive sites often host outdated images. An old image can still be installed and updated, but it wastes time and may predate important fixes. The official download page always carries the current image, so there is no reason to accept a stale copy from elsewhere.

Treating the nano image like an installer

Nano is preinstalled and runs from the card you write it to. If you wanted a traditional installation onto an internal SSD, you wanted the vga or serial image instead.

How the releases and images fit together

Understanding the release rhythm helps you interpret what the download page shows. OPNsense publishes two major Community Edition releases per year, in January and July, and the version number is simply the year and month: 26.7 means July 2026. Each major release is followed by minor updates roughly every two weeks, which fix bugs and address security advisories. The 26.7 series, for example, had reached 26.7.9 by 11 November 2026, including new security advisories for the core system.

Installer images follow the majors, not the minor updates. That is why the download is labelled 26.7 while the newest update is 26.7.9, and it is also why an image you downloaded a few months ago is not necessarily obsolete: if it belongs to the current series, installing it and updating afterwards reaches exactly the same end state. What you should avoid is installing from an image of an older series when a newer major exists, because crossing a major release boundary during updates is a bigger step than catching up within one series. The release notes for the series, published in the official documentation, list the image checksums and the signing key for that series, which makes them a good second source for verification.

Questions people ask before downloading

Is OPNsense really free?

Yes. The Community Edition is open source and free to download and use, including for the firewall of a small business. The paid Business Edition is a separate subscription aimed at organisations that want a more conservative upgrade path and commercial extras; nothing about the free edition is time-limited or feature-locked for ordinary use.

Can I install OPNsense in a virtual machine instead?

Yes, and the download is the same page. The official virtual machine guidance uses the dvd ISO image, because a hypervisor can boot a VM directly from an ISO file without any USB drive. If that is your plan, download the dvd type and attach it to the virtual machine as its optical drive.

Which file do I pick for a USB installer?

The vga image for hardware with a display, or the serial image for headless hardware. Both arrive as .img files (compressed with .bz2) and are written to the drive as raw images, not copied as files.

What to do next

With a verified image on your computer, the path forward is short. First, write the image to a USB drive (or directly to the card or drive for nano) by following How to Create an OPNsense Bootable USB Drive. Then boot the firewall hardware from that drive and work through the OPNsense Installation Guide, which covers the installer, disk choices and the first reboot into the console menu. Finally, once the system is up, run the firmware update check (System, then Firmware, then Status) to move from the 26.7 image to the latest update in the series, currently 26.7.9. At that point your download has become a current, fully patched firewall.

Keep going in Download & Install