Skip to content

CEF v151 Documentation

CEF build: 151.3.24+g2384915+chromium-151.0.7922.174 (commit 3584) API version: 15100

Start here — this is the latest documented version

All APIs documented in this reference are pinned to CEF 151.3.24. APIs gated behind CEF_API_ADDED(N) are noted in the source file comment for each method. Prefer offline reading? Grab the PDF manual.

Where to go next

Pick the area that matches what you are building:

  • Core APIs — start with CefApp, CefClient and CefBrowser. Everything about process bootstrap, browser lifecycle, frames, DOM, requests and data objects lives here.
  • Browser Handlers — the interfaces you implement and return from CefClient to customize behavior: display, dialogs, downloads, context menus, audio, drag & drop and more.
  • Views Framework — the browser-process UI toolkit if you build native windows: CefWindow, CefPanel, layouts, buttons and textfields.
  • V8 & Process Messaging — executing and bridging JavaScript: the CefV8 value tree, CefProcessMessage IPC and shared memory regions.
  • System Utilities — the supporting cast: tasks and threads, parsers, streams, cookies, URL requests, scheme registration and constant tables.

Categories at a glance

CategoryDescriptionFiles
Core APIsFoundational interfaces: process bootstrap, browser lifecycle, frames, DOM, requests, and data objects.24
Browser HandlersUser-implemented handler interfaces returned from CefClient and registered with CefBrowserHost.25
Views FrameworkBrowser-process UI toolkit: windows, panels, layouts, buttons, textfields, and their delegates.22
V8 & Process MessagingJavaScript bridge, value tree, inter-process messages, shared memory regions.5
System UtilitiesTasks, threads, parsers, streams, cookies, URL requests, scheme registration, and constant tables.29

How to read these pages

Each page documents one include/*.h header. The structure is consistent across the whole reference, so once you have read one page you can navigate any of them:

  1. Header — the source filename.
  2. Overview — one-sentence category context.
  3. Per-interface section## ClassName for each class/interface in the header.
  4. Each section lists:
    • Source File
    • Process / Thread Context
    • Purpose
    • Notable Members (for constant-table headers)
    • Methods (with Parameters, Return Value, Usage, Threading Constraint)
    • Usage Example (a cpp code block)
  5. See Also — relative links to related interfaces.

Threading constraints

Where the source header does not specify a threading constraint, this site explicitly writes "Threading constraint not specified in source." Do not infer one.

Attribution

Curated, generated and maintained by Ernest Tech House — an independent organization, separate from the official CEF maintainers. This is not yet the official CEF documentation.

Derived from the CEF C++ headers — © Marshall A. Greenblatt, Google Inc. & contributors (BSD-style license). Not an official CEF project.