Develop desktop applications with Chromium Embedded Framework on Windows on Arm
Introduction
Create a Chromium Embedded Framework Project
Next Steps
Develop desktop applications with Chromium Embedded Framework on Windows on Arm
Who is this for?
This learning path is for developers who want to learn how to use web technologies for developing Desktop apps on Windows on Arm (WoA).
What will you learn?
Upon completion of this Learning Path, you will be able to:
- Create and build a Chromium Embedded Framework (CEF) project using CMake
- Modify and style the application
Prerequisites
Before starting, you will need the following:
- A Windows on Arm computer such as the Lenovo Thinkpad X13s running Windows 11 or a Windows on Arm virtual machine .
- Visual Studio 2022.
Summary
This summary was drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.
You’ll create a CEF desktop application on Windows on Arm using CMake and C++. First, you’ll configure the project for Visual Studio 2022, build it, and launch a Chromium-based window. Then, you’ll integrate local HTML, CSS, and JavaScript assets to build a project that you can iterate on with familiar web technologies.
Frequently asked questions
These FAQs were drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.
Pick the Visual Studio generator that matches your installed Visual Studio 2022. If you open the folder as a CMake project in Visual Studio, let the IDE configure it and choose a configuration that targets Windows on Arm.
A desktop window backed by Chromium should launch and render the default page included in the project. Seeing a basic template or sample content confirms the embedded browser is running.
Place assets in the locations referenced by the starter project or by paths in the application code. If the content doesn’t appear, check that the file paths are correct relative to the working directory used at runtime.
Check the build output for the target platform when you run
cmake -G "Visual Studio 17" -A arm64 -B build before building.Verify that the initial URL or local file path the application loads is correct and accessible. Update the asset location or move the assets to the expected location, then rebuild and run again.