Library:Chromium Embedded Framework
| Vendor | Marshall Greenblatt and contributors |
|---|---|
| Uses | Library:V8 |
| License | BSD-3-Clause |
| Website | https://github.com/chromiumembedded/cef |
| On this wiki | Facts · Code · Notes · Topics |
CEF is a BSD-3-Clause C/C++ framework that embeds a Chromium browser in native applications (game launchers, chat clients, tools); apps ship libcef.dll plus a multi-process helper layout and are recognisable by the cef_ export prefix and a CEF/Chromium version string.
Overview
CEF wraps the Chromium content layer. A host application links a small C++ wrapper (libcef_dll_wrapper, built from the CEF distribution) that calls the C API exported by libcef.dll (Windows), libcef.so (Linux) or Chromium Embedded Framework.framework (macOS). Many launchers and overlay tools embed it, so finding libcef is often the first step to locating where web content, cookies and JavaScript bridges live.
Identification
- Files next to the executable:
libcef.dll,chrome_elf.dll,icudtl.dat,resources.pak,chrome_100_percent.pak,locales\*.pak,v8_context_snapshot.binorsnapshot_blob.bin,libEGL.dll,libGLESv2.dll,d3dcompiler_47.dll,vk_swiftshader.dll. Unverified: the exact list differs by CEF branch. - Exports: the C API functions carry the
cef_prefix (CEF_EXPORT in include/internal/cef_export.h marks them dllexport or default visibility). The version exports arecef_version_info(int entry),cef_version_info_all,cef_version_full()(newer API versions) andcef_api_hash(int version, int entry)/cef_api_version(); the C++ namesCefInitializeandCefExecuteProcesslive in the wrapper, not the DLL.cef_initializeandcef_execute_processare the C API entry points: docs/using_the_capi.md (same commit) callscef_execute_process(&main_args, &app->app, NULL)(line 569) andcef_initialize(&main_args, &settings, &app->app, NULL)(line 583) from plain C, and tests/cefsimple_capi/cefsimple_win.c is the sample that does so. Unverified: that they appear in the export table by exactly these names (the capi headers are generated and not in the checkout). - Version: see Fact:Chromium Embedded Framework/identification/Version information. A full version string looks like
143.0.3+gcbafc77+chromium-143.0.7499.0(CEF major.minor.patch, git hash, Chromium version). The Chromium revision a branch builds against is recorded in CHROMIUM_BUILD_COMPATIBILITY.txt.
Subprocess model
CEF is multi-process like Chromium. The same executable (or a separate helper exe named in CefSettings.browser_subprocess_path) is started with --type=renderer, --type=gpu-process, --type=utility and so on; the browser process has no --type switch. The host calls CefExecuteProcess first: for a subprocess it runs the process and returns an exit code, for the browser process it returns -1 and the host continues to CefInitialize (documented in include/cef_app.h). So a launcher often appears as many identical processes in a process list; attach to the one without --type. The Windows sandbox is created with cef_sandbox_info_create() (include/cef_sandbox_win.h) and can be turned off with the no-sandbox switch.
Related
Library:V8 (JavaScript engine inside libcef), Library:Electron (same Chromium base, different embedding), Library:WebView2, Technique:Identifying C++ utility libraries.
Code & repositories
- https://github.com/chromiumembedded/cef (BSD-3-Clause)
- https://github.com/chromiumembedded/cef @
a875f407e36bdf4fe6c31622e150ce73f77629c8· license: BSD-3-Clause (read from LICENSE.txt; GitHub's detector did not classify it)
CEF headers: version info exports, app/process startup, sandbox.
Tested on: source read, not run: source read · checked 2026-10-18; last activity 2026-10-16