explaingit

sandboxie/sandboxie

3,633CAudience · ops devopsComplexity · 3/5LicenseSetup · moderate

TLDR

A Windows application that runs programs in an isolated sandbox so any file system or registry changes are discarded when you close it, protecting the real system.

Mindmap

mindmap
  root((Sandboxie))
    What it does
      Isolate programs
      Redirect file writes
      Protect real system
    How it works
      Kernel-level driver
      System call interception
      Contained sandbox folder
    Use cases
      Run untrusted software
      Test installers
      Isolated browsing
    Audience
      Security researchers
      Power users
      Developers testing
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Things people build with this

USE CASE 1

Run an unknown or untrusted Windows executable safely without risking permanent changes to your system.

USE CASE 2

Test a software installer to see what it installs and where before committing to a real installation.

USE CASE 3

Browse the web in an isolated container so browser-based attacks cannot affect your actual Windows installation.

Tech stack

CWindows

Getting it running

Difficulty · moderate Time to first run · 30min

Requires Windows and kernel driver installation, compatibility depends on Windows version.

License terms are not specified in the available documentation.

In plain English

Sandboxie is a Windows application that runs programs inside an isolated container. When software runs inside Sandboxie, any changes it tries to make to the file system, the Windows registry, or other system areas are redirected to a separate, contained space. When you close the sandbox and discard its contents, those changes disappear, leaving the real underlying system completely unaffected. This isolation is useful in several situations. You can run unfamiliar or untrusted software without risking permanent changes to your system. You can test installers to see what they actually do before committing to a real installation. You can browse the web with an extra layer of separation between your system and whatever a website might try to do. Since everything the sandboxed program does is contained, discarding the sandbox completely undoes it. Sandboxie has a long history as a Windows security and testing tool. It was originally commercial software sold by its original developers, then acquired and later made open source. This repository contains the C codebase for the application, including a kernel-level driver that intercepts system calls and a user interface for managing sandbox configurations. The intended audience includes security researchers, developers who want to test software safely, and privacy-conscious users who want an additional layer of protection when running programs they do not fully trust. Because Sandboxie operates at the Windows kernel level, it involves low-level system components that require careful installation and are sensitive to Windows version changes. Maintaining compatibility with new Windows releases requires ongoing work, which the open-source community around this repository handles. It is a specialized tool suited to technically comfortable users rather than a simple consumer application.

Copy-paste prompts

Prompt 1
How do I create a new sandbox in Sandboxie and run a specific program inside it so its file changes stay contained?
Prompt 2
What is the difference between running a program in Sandboxie versus inside a virtual machine for security purposes?
Prompt 3
How does Sandboxie intercept file system and registry calls at the Windows kernel level to redirect them to the sandbox folder?
Prompt 4
Set up Sandboxie to automatically delete sandbox contents when I close the sandboxed program, so nothing is left behind.
Open on GitHub → Explain another repo

← sandboxie on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.