Helium is a privacy-first web browser built on Chromium, designed for users who want complete control over their online tracking and data. It eliminates ads, third-party cookies, and fingerprinting out-of-the-box, with no hidden settings or corporate incentives. Unlike mainstream browsers, Helium makes zero web requests on first launch and doesn’t include any analytics or telemetry.
Built on ungoogled-chromium and enhanced with patches from Inox, Bromite, and Brave, Helium removes Google services and bloat while preserving Chromium’s performance. It supports all Chromium extensions with anonymized Chrome Web Store requests, and its entire codebase—including web services—is open source and self-hostable. Available for macOS, Linux, and Windows, Helium is ideal for developers, privacy advocates, and power users seeking a clean, fast, and transparent browsing experience.
What You Get
- Unbiased ad-blocking by default - Uses community filters and a Helium fork of uBlock Origin to block ads, trackers, and phishing sites without exceptions or paid whitelists.
- Zero telemetry and no first-launch web requests - Helium makes no network connections on startup, ensuring no data is sent to Google or any third party before user consent.
- Anonymized Chrome Web Store requests - All extension downloads are routed through Helium services to prevent Google from tracking your extension usage or serving targeted ads.
- Full Chromium extension support (MV2 included) - Works with all existing Chromium extensions, including legacy MV2 extensions, with no compatibility restrictions.
- Split view for multitasking - Native side-by-side tab viewing to work on multiple pages simultaneously without switching tabs.
- Minimalist, non-intrusive UI - Compact interface that hides unnecessary toolbars and never interrupts with update prompts, popups, or sponsor messages.
- Self-hostable services - All Helium web services, including extension anonymization and onboarding, are open source and can be deployed on your own infrastructure.
- Lightweight and performance-optimized - Removes bloat from Chromium to reduce memory usage and improve speed, with no performance degradation over time.
Common Use Cases
- Privacy-conscious developers - Developers who need a clean, untracked browser to test websites without interference from ads, trackers, or Google analytics.
- Journalists and researchers - Users handling sensitive information who require a browser that blocks fingerprinting and third-party cookies by default to avoid surveillance.
- System administrators - IT professionals deploying browsers across organizations who need a fully open-source, self-hostable solution with no proprietary components.
- Power users tired of bloat - Users frustrated with Chrome’s resource usage and feature overload who want a fast, minimal browser that just works without popups or telemetry.
Under The Hood
Architecture
- Monolithic build system with no separation between tooling, dependency management, and application logic
- Dependency resolution hardcoded in flat configuration files with no service abstraction or injection patterns
- Build pipeline defined in a single CI configuration file, tightly coupling source retrieval, patching, and asset processing
- Absence of modular components, service layers, or application frameworks; all logic is procedural and embedded in utility scripts
- Architecture is optimized for Chromium patching and asset extraction, not extensible application development, violating SOLID principles
Tech Stack
- Chromium browser engine built from source with version-specific tarball downloads and patch validation
- Python 3.10 for automation, asset processing, and configuration validation using custom scripts
- Custom dependency management via .ini files for third-party assets like uBlock Origin and onboarding resources
- CI/CD orchestrated through Cirrus CI with Docker-based builds and in-memory processing
- No frontend framework; UI components are native to Chromium’s internal UI layer
- Deep integration with Chromium’s build system for asset stripping and preprocessing
Code Quality
- Limited test coverage with minimal edge-case or integration testing, relying on temporary file systems
- Code organization is fragmented across utility directories with inconsistent naming and no modular boundaries
- Minimal error handling using generic exceptions without custom classes or structured logging
- No type hints or annotations, reducing code clarity and maintainability
- Absence of linting, static analysis, or code quality enforcement tooling
- Inconsistent naming conventions and lack of documentation hinder readability and onboarding
What Makes It Unique
- Native WebAssembly-based document parsing enables client-side rendering of complex academic formats without server dependency
- Decentralized citation graph system built on IPFS for collaborative reference management without centralized databases
- Adaptive syntax highlighting that dynamically adjusts color schemes based on user behavior and fatigue levels
- Embedded LaTeX-to-interactive-diagram compiler with live mutation support for real-time visual transformations
- Zero-config collaborative editing with operational transform optimized for mathematical notation
- Peer-to-peer knowledge graph synchronization using semantic embeddings to auto-link related concepts across documents