cefsharp/cefsharp

.NET (WPF and Windows Forms) bindings for the Chromium Embedded Framework

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 14 minutes ago
Added to GitGenius on September 6th, 2026
Created on December 3rd, 2010
Open Issues & Pull Requests: 71 (+0)
GitHub issues: Enabled
Number of forks: 2,923
Total Stargazers: 10,254 (+0)
Total Subscribers: 520 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Issue API getrepoissuespagesummary failed: 429 Rate limit exceeded. Please try again later.

Detailed Description

CefSharp is a .NET wrapper that lets you embed Chromium in Windows desktop applications built with WPF or Windows Forms. It provides bindings to the Chromium Embedded Framework, with approximately 30% of the code written in C++/CLI and the remainder in C#, making it usable from C#, VB.NET, or any other CLR language.

The tool solves the problem of integrating a modern web browser engine into .NET desktop applications. Rather than building a browser from scratch, CefSharp wraps the Chromium Embedded Framework, allowing developers to leverage Chromium's rendering and JavaScript capabilities within their desktop UI frameworks. The wrapper handles the interop layer between managed .NET code and the native CEF library.

Developers building Windows desktop applications that need embedded web content should consider CefSharp if they are already invested in the .NET ecosystem and targeting WPF or WinForms. The project offers multiple deployment options through NuGet packages: separate packages for WinForms, WPF, and off-screen rendering, plus an alternative HwndHost-based WPF implementation for scenarios where data binding support is needed. The tool is suitable for applications ranging from simple embedded browsers to complex scenarios requiring fine-grained control over rendering and JavaScript interaction. The README does not compare CefSharp to alternative approaches.

The project maintains active discussion channels on GitHub for questions and maintains comprehensive documentation including example projects, a general usage guide, FAQ, and API reference. The team enforces a clear separation between the issue tracker for bug reports and pull requests, with contribution guidelines documented for prospective contributors. A changelog is available to help users understand breaking changes when upgrading between versions.