Browser Developers

Embedded (CEF)

CEF Transparency

A company-internal Chromium Embedded Framework (CEF) transparency build.

  • CEF
  • Chromium
  • C++
  • Embedded browser

What was built

CEF Transparency is an internal build of the Chromium Embedded Framework (CEF), made for a company’s own use rather than as a public product. CEF lets a native application embed a Chromium-based browser inside its own window, so the host application can render web content while keeping its own window chrome, controls and behavior. Building it in C++ means working directly against Chromium’s embedding API rather than a higher-level wrapper, which gives the host application more control over how the embedded browser is created, sized and updated.

The engineering challenge

CEF lets an application host Chromium inside its own window. That gives the app modern web rendering while the app itself stays in control of the surrounding window and behaviour. This is the pattern behind internal tooling that needs to show live or rendered web content inside a desktop application, without shipping a separate, full browser to its users. Because it is internal tooling rather than a public release, there was no store listing, installer or update channel to build — just the embedded browser itself and the C++ code that connects it to the host application.

How it works

  • Diagram of an application window with native controls and a region rendered by the Chromium Embedded Framework
    Illustration: how CEF places Chromium inside an application window.

Engineering scope and what shipped

  • A custom Chromium Embedded Framework (CEF) build
  • Built for internal company use

Engineering approach: how it fits together

How CEF Transparency fits inside the host application

  1. Host application

    The internal company application, with its own native window, menus and controls.

  2. CEF integration

    The C++ code that creates, sizes and updates the embedded browser view inside the host window.

  3. Chromium Embedded Framework

    CEF wraps the Chromium rendering engine for embedding inside another application.

  4. Internal build and release

    Built and distributed for the company’s own internal use, with no public store listing or installer.

  • Your product
  • Our engineering
  • Upstream, kept as close to unmodified as possible
  • Platforms and release
The host application keeps its own window and controls; only the content area is rendered by the embedded Chromium engine.

Related services

Facing a similar engineering problem?

Tell us what you are building. A browser engineer will walk you through how we would approach it, what is hard about it and what it takes to maintain.

Tell Us What You're Building