Inside Samsung Internet: Chromium, One UI, and Extensions

This article explores the architecture of the Samsung Internet browser on Galaxy phones. It examines how Samsung utilizes the open-source Chromium engine for core web rendering while simultaneously integrating its proprietary One UI interface and a custom API framework that allows third-party content blocker extensions to function seamlessly.

Leveraging the Chromium Engine

Samsung Internet is built on the open-source Chromium project, the same foundational code used by Google Chrome and Microsoft Edge. By using Chromium, Samsung inherits the Blink rendering engine and the V8 JavaScript engine. This ensures that web pages load quickly, adhere to modern web standards, and receive regular upstream security patches.

Instead of building and maintaining a web rendering engine from scratch, Samsung engineers fork the Chromium source code and optimize it specifically for the hardware architectures—such as Snapdragon and Exynos processors—found in Galaxy phones. This hardware-level optimization allows Samsung Internet to handle multi-threading, GPU acceleration, and memory management more efficiently on Galaxy devices than generic browsers.

Applying Custom One UI Styling

While Chromium handles the invisible work of processing HTML, CSS, and JavaScript, Samsung completely strips away the default Chromium user interface. In its place, Samsung layers its proprietary One UI design framework.

One UI is engineered for one-handed usability on large smartphones. Samsung achieves this in the browser by decoupling the UI layer from the Chromium core, allowing them to relocate the address bar, tab manager, and navigation controls to the bottom of the screen. Furthermore, the One UI layer hooks directly into the Chromium rendering pipeline to offer custom visual features. For example, when a Galaxy phone is set to Dark Mode, Samsung Internet intercepts the webpage's CSS before it is displayed, dynamically inverting light backgrounds and adjusting image contrast to match the system-wide aesthetic.

Enabling Content Blocker Extensions

The mobile version of Google Chrome does not support extensions, despite being built on Chromium. Samsung overcomes this limitation on Galaxy phones by building a custom Content Blocker API directly into its modified Chromium network stack.

Rather than running desktop-style extensions that consume heavy system resources and drain the battery, Samsung's implementation relies on a filter-list model. Users download approved content blocker applications from the Galaxy Store or Google Play Store. These apps do not actively monitor traffic themselves; instead, they pass a compiled list of blocking rules (such as URLs of known ad servers and tracking scripts) to Samsung Internet via the Content Blocker API.

When a user requests a webpage, Samsung Internet's Chromium engine cross-references every network request against these imported filter lists. If a request matches a blocked rule, the browser cancels the connection before the data is downloaded. This approach keeps the browser fast, protects user privacy, and reduces mobile data consumption without compromising the stability of the underlying Chromium engine.