Paid

Download · v0.1.42

Get Splitser.

Installers for Linux, Windows and macOS. The macOS builds are signed and notarised, so they open normally. Windows and Linux are not signed yet, so Windows will object the first time -- there are instructions for that below, and checksums on every file if you would rather verify than trust.

Linux

Debian / Ubuntu

x86_64 Run by us

Installed and run on Linux.

sudo apt install ./Splitser-0.1.42-amd64.deb
.deb 87 MB

AppImage

x86_64 Untested

Built on CI, not yet run by us. No install, no root -- mark it executable and run it. Works on any distribution, so it is the one to take if you are not on Debian/Ubuntu or Fedora/RHEL.

chmod +x Splitser-0.1.42-x86_64.AppImage && ./Splitser-0.1.42-x86_64.AppImage

Two things can stop an AppImage starting, and neither means a bad download. If the error mentions libfuse.so.2: Ubuntu 22.04+ and Mint 21+ no longer ship FUSE 2, which an AppImage uses to mount itself -- run sudo apt install libfuse2, or use the command below to skip FUSE entirely. If instead it aborts saying chrome-sandbox must be owned by root: that is Ubuntu 24.04+ specifically, whose AppArmor policy closes the fallback an AppImage would otherwise use -- the same file runs sandboxed on Fedora, so it is your distribution's policy rather than a broken download. An AppImage cannot fix it itself, because it never runs an installer. You will see --no-sandbox suggested for this; we would rather you did not, as it switches off the isolation that keeps a web page away from the rest of your machine. On Debian or Ubuntu, take the .deb above -- it installs that helper properly and keeps the sandbox on.

./Splitser-0.1.42-x86_64.AppImage --appimage-extract-and-run
.AppImage 127 MB

Fedora / RHEL

x86_64 Untested

Built on CI, not yet run by us.

sudo dnf install ./Splitser-0.1.42-x86_64.rpm

Upgrading from 0.1.21-0.1.24 and dnf stops with a scriptlet error about "/usr/bin/splitser has not been configured as an alternative"? That is the outgoing package's own uninstall script, which runs during the upgrade before the fixed one can take over -- so this version is the last that triggers it, and the first that no longer ships it. It happens once. Clear the old package without running its script, then install normally, and no upgrade after this one will do it again. A FRESH install is unaffected -- this only happens when an older package is being replaced:

sudo rpm -e --noscripts splitser
.rpm 88 MB

Windows

Windows installer

x64 Untested

Built on CI, not yet run by us. Unsigned, so SmartScreen will step in the first time -- see below.

.exe 101 MB

macOS

macOS -- Apple Silicon

arm64 (M1 and later) Untested

Built on CI, not yet run by us. Signed with a Developer ID and notarised by Apple, with the ticket stapled to the disk image -- so it opens normally, with no "unidentified developer" warning to talk your way past.

.dmg 119 MB

macOS -- Intel

x86_64 Untested

Built on CI, not yet run by us. Signed with a Developer ID and notarised by Apple, with the ticket stapled to the disk image -- so it opens normally, with no "unidentified developer" warning to talk your way past.

.dmg 123 MB

— or verify with sha256sum -c SHA256SUMS (shasum -a 256 on macOS).
The same 6 files are attached to the GitHub release if you would rather get them there — byte-for-byte identical, so the checksums above describe either copy.

SHA-256 · v0.1.42

Published here on splitser.org, not alongside the files — so write access to the download host isn't enough to forge a matching hash.

  • Splitser-0.1.42-amd64.deb
    f77523f16a4a9d0986cfbf18fc0a5d925367fadf7602c5673d18a48150d749c0
  • Splitser-0.1.42-x86_64.AppImage
    89e8baf558de3ce7fa5adf404792c230adbca0fd50a967992c0f87e1d360c880
  • Splitser-0.1.42-x86_64.rpm
    0248d46804beed3e0e8d2ccc263171c6dcdbeced671c8b7904e7f1cc4e58b5ee
  • Splitser-0.1.42-x64.exe
    3aecc04b6c3d2d1296941ea6675e858116fb18e580b33b62b2c950e3a0e26839
  • Splitser-0.1.42-arm64.dmg
    6bb1c77886bd714538ca1383b4498ec033d5f775ce18261fde25711368f03777
  • Splitser-0.1.42-x64.dmg
    0aa9b522376d78c83eec982348cf9f0bcc6998e36a63475c16079fa25e62700e

Download SHA256SUMS for sha256sum -c.

What your OS will say, and what to do about it

Code signing means paying a certificate authority -- and on macOS, Apple -- so your operating system can tell who published a program. That is now done for macOS and not yet for Windows. Where a warning still appears it is accurate: your computer genuinely cannot tell who built the file, and that is worth taking seriously here and everywhere else. Check the SHA-256 above if you would rather have certainty than trust.

Windows

SmartScreen will say "Windows protected your PC" and hide the run button behind More info. Click that, confirm the publisher is unknown, then Run anyway.

If you end up with a .crdownload file instead of an installer, the browser finished downloading but never renamed it -- Chromium-based browsers use that extension for a download in progress, and an unsigned executable sometimes gets left that way. Rename it so it ends in .exe and it will run.

Check it first, though: a .crdownload can also mean the download really was cut short, and a truncated installer is worth catching before you run it. In PowerShell, from your Downloads folder: 

Get-FileHash .\Splitser-0.1.42-x64.exe.crdownload -Algorithm SHA256
Rename-Item .\Splitser-0.1.42-x64.exe.crdownload Splitser-0.1.42-x64.exe

If the hash matches the SHA-256 published above, the file is intact and the rename is all it needed. If it doesn't match, download it again. (Explorer hides extensions by default -- turn on View › File name extensions, or just use the command above.)

macOS

Nothing to work around. The disk image is signed with a Developer ID and notarised by Apple, with the ticket stapled to it, so Gatekeeper recognises the publisher: open the .dmg, drag Splitser to Applications, and double-click it like anything else. No right-click-Open trick, no trip to Security settings. Take the Apple Silicon build for an M-series Mac, Intel for anything older.

Linux

No signing gate. apt and dnf may note the package isn't from a repository, which is expected for a downloaded file. The AppImage needs nothing beyond chmod +x.

Or build it yourself

Two dependencies, no native modules, nothing to compile. Reading the source before running an unsigned binary is an entirely reasonable thing to want.

1

Get the source

git clone https://github.com/MIR-2025/splitser.git
cd splitser
2

Install and start

npm install
npm start

npm start passes --no-sandbox, because an npm-installed Electron ships chrome-sandbox without the SUID-root bit on Linux. That's a development convenience, not how the packaged builds above run.

3

Or keep it running after you close the terminal

./splitser          # start, detached
./splitser status
./splitser stop

Where each platform actually stands

One Electron codebase, no per-OS forks. But "it built" and "someone ran it" are different claims -- Linux and Windows can make the second one, macOS cannot yet.

Linux

Verified

Run on Ubuntu and Linux Mint

Developed on X11 / XFCE and used daily. The current build was installed from the .deb and run on Ubuntu and Mint.

Minimum A current mainstream distribution (Chromium 150 wants a recent glibc), X11 or Wayland

macOS

Built, untested

Built on CI, never run by us

Two disk images come out of the build, one for Apple Silicon and one for Intel, signed with an Apple Developer ID and notarised by Apple. Nobody here has a Mac to try either on.

Minimum macOS 12 (Monterey) or newer, Apple Silicon or Intel

Windows

Verified

Installed and run on Windows 10

The NSIS installer has been installed and run on Windows 10, most recently the current build. x64 only -- there is no arm64 build.

Minimum Windows 10 or newer, x64

Minimums track Electron 43 / Chromium 150, the version the app pins today. They move whenever that pin moves -- Chromium 150 is the last to support macOS 12, for instance.

What it needs, and where it puts things

Runtime
Electron 43 (Chromium 150) -- that is the whole runtime
Dependencies
Two: electron, and @ghostery/adblocker-electron for the shields. No native modules, so nothing compiles per platform
Network
A one-time fetch of the ad-block filter list, then cached. No server, no account, no sync, no telemetry
Your data
~/.config/splitser · ~/Library/Application Support/splitser · %APPDATA%\splitser

That directory holds history.json, bookmarks.json, session.json and settings.json as plain readable JSON, plus vault.enc as AES-256-GCM ciphertext. Back it up or delete it; it's your data and it never leaves the machine.

What isn't built

Stated as plainly as the feature list, so you can tell which is which.

Code signing on Windows and Linux, and auto-update

The macOS builds are signed with a Developer ID and notarised by Apple, so they open without a warning. Windows and Linux are not signed yet, so SmartScreen will still step in on Windows. Nothing auto-updates on any platform -- you re-download to upgrade.

Chrome extensions

Ad and tracker blocking is built in and on by default -- but loading your own Chrome extensions is not. Electron supports unpacked extensions with only partial API coverage.

Mobile

Desktop only. There is no mobile build and none planned yet.

What should it do next?

The roadmap isn't settled -- it's a preview, and what's missing is a question rather than a decision. If something you need isn't here, or something that is here gets in your way, say so and it goes on the list.

Suggest something Or just tell us

The issue tracker needs a GitHub account; the form doesn't. Or email browser@splitser.org.