fathyb / carbonyl

O O \ / O —— Cr —— O / \ O O Carbonyl Carbonyl is a Chromium based browser built to run in a terminal. Read the blog post. It supports pretty much all Web APIs including WebGL, WebGPU, audio and video playback, animations, etc.. It's snappy, starts in less than a second, runs at 60 FPS, and idles at 0% CPU usage. It does not require a window server (i.e. works in a safe-mode console), and even runs through SSH. Carbonyl originally started as and is now the runtime behind it. Usage > Carbonyl on Linux without Docker requires the same dependencies as Chromium. Docker npm Binaries • macOS amd64 • macOS arm64 • Linux amd64 • Linux arm64 Demo Known issues • Fullscreen mode not supported yet Comparisons Lynx Lynx is the original terminal web browser, and the oldest one still maintained. Pros • When it understands a page, Lynx has the best layout, fully optimized for the terminal Cons > Some might sound like pluses, but Browsh and Carbonyl let you disable most of those if you'd like • Does not support a lot of modern web standards • Cannot run JavaScript/WebAssembly • Cannot view or play media (audio, video, DOOM) Browsh Browsh is the original "normal browser into a terminal" project. It starts Firefox in headless mode and connects to it through an automation protocol. Pro • It's easier to update the underlying browser: just update Firefox • This makes development easier: just install Firefox and compile the Go code in a few seconds • As of today, Browsh supports extensions while Carbonyl doesn't, although it's on our roadmap Cons • It runs slower and requires more resources than Carbonyl. 50x more CPU power is needed for the same content in average, that's because Carbonyl does not downscale or copy the window framebuffer, it natively renders to the terminal resolution. • It uses custom stylesheets to fix the layout, which is less reliable than Carbonyl's changes to its HTML engine (Blink). Operating System Support As far as tested, the operating systems under are supported: • Linux (Debian, Ubuntu and Arch tested) • MacOS • Windows 11 and WSL Contributing Carbonyl is split in two parts: the "core" which is built into a shared library ( ), and the "runtime" which dynamically loads the core ( executable). The core is written in Rust and takes a few seconds to build from scratch. The runtime is a modified version of the Chromium headless shell and takes more than an hour to build from scratch. If you're just making changes to the Rust code, build and replace it in a release version of Carbonyl. Core Runtime Few notes: • Building the runtime is almost the same as building Chromium with extra steps to patch and bundle the Rust library. Scripts in the directory are simple wrappers around , , etc.. • Building Chromium for arm64 on Linux requires an amd64 processor • Carbonyl is only tested on Linux and macOS, other platforms likely require code changes to Chromium • Chromium is huge and takes a long time to build, making your computer mostly unresponsive. An 8-core CPU such as an M1 Max or an i9 9900k with 10 Gbps fiber takes around ~1 hour to fetch and build. It requires around 100 GB of disk space. Fetch > Fetch Chromium's code. Apply patches > Any changes made to Chromium will be reverted, make sure to save any changes you made. Configure > is the target name, you can use multiple ones and pick any name you'd like, i.e.: > > When prompted, enter the following arguments: Build binaries This should produce the following outputs: • : browser binary • • • • Build Docker image Run