Desktop tools remain useful
Arrange available PC readings, music, volume and other widgets on your desktop or second screen. A game does not need to be running for that workspace to have a purpose.
System Requirements
Bring useful PC readings, capture and everyday controls into a workspace that suits your setup. Check the Windows and Overwolf baseline, then choose a desktop layout, supported game Overlay, second monitor or phone companion. Start with the tools you use most and add more as your routine grows.
Your setup, in three checks
Use these three checks to prepare your Windows PC, the current Overwolf package and the features you want to use.
Quick answer
The current Overwolf build needs Windows 10 1809+ or Windows 11, .NET Framework 4.8 and Overwolf Client 0.294.0.18 or later. Start with available desktop widgets, then check the game, display, sensor or media support for the features you want. A second screen or paired phone gives those controls another useful place beside your game.
The current package
Requirements updated .
| Requirement | Current baseline | What to confirm |
|---|---|---|
| Windows | Windows 10 version 1809+ or Windows 11; bundled native integration targets x64. | Check the Windows version and system type on the PC that will run the app. |
| .NET runtime | .NET Framework 4.8 for the bundled Windows plugin. | Follow the complete package's runtime instructions; the .NET SDK is a different tool. |
| Overwolf Client | 0.294.0.18 or newer is the current package's declared minimum. | Use a current compatible client and the distribution instructions for your build. |
| Package access | Official Overwolf store release or verified setup package. | Download SysCubes directly for Windows 10/11 through the official release installer. |
The Windows integrations are bundled with the Overwolf package. Players using a complete build need the runtime requirements above; Node.js, a source checkout and the .NET SDK are tools for developers. Check the release instructions for your build to take the right installation route.
Choose your gaming workspace
Arrange available PC readings, music, volume and other widgets on your desktop or second screen. A game does not need to be running for that workspace to have a purpose.
Check the exact title and edition in Overwolf's supported-games list. Then enable the running game's SysCubes profile and test the visible Overlay in that game's supported display mode.
Check the game FPS reading during play, or save a short capture with picture and audio before a match you want to keep. A quick test makes your chosen monitoring or recording routine ready for the session.
Check your title and edition in the current Overwolf supported-games reference, including its display-mode guidance. Its current guidance excludes Microsoft Store game editions. When an in-game integration is unavailable, keep supported PC readings and controls on the desktop or a second-screen dashboard.
Build around available capabilities
| Feature | What it depends on | Useful first test |
|---|---|---|
| Game Overlay | Overwolf support, current game/display configuration and enabled widgets in the correct profile. | Show one visible widget and confirm its interaction mode. |
| Game FPS | A supported running-game FPS source. | Check an available changing FPS reading during actual gameplay. |
| Hardware readings | Supported sensors and the access path the current native integration exposes. | Compare available readings and inspect the app's status for a missing sensor. |
| Game recording / Replay | Overwolf capture support, display/source configuration and a writable destination. | Save a short test and verify its picture, audio and file location. |
| Monitor brightness | A supported DDC/CI external display path or laptop WMI brightness interface. | Adjust one small level and verify the intended physical screen. |
| Media / app volume | An exposed Windows media session or an available Windows audio playback session. | Start playback, select the intended source and test one small control. |
| Processes | Available Windows native process readings. | Search for a recognized app and inspect CPU and memory samples. |
Choose the features that help your session, then use their individual documentation for setup. Checking your actual sensors, display and capture workload helps you build a workspace that suits your PC.
Use the phone you already have
Run SysCubes on the PC. Connect the phone to Wi-Fi that can reach the PC's local address; the PC can use Ethernet or Wi-Fi on that trusted LAN.
Use the PC's current Phone Companion address or QR code. Pair in the phone's browser with the current code; no separate mobile app is required.
Choose the information and controls you want shared. Verify a small supported action on the PC before relying on the companion during a game.
Use the right route for the build
SysCubes for Windows is available to download via Overwolf. The download page lists current Windows release status. Use the link and instructions for your available channel to prepare the complete app package.
If you have an approved test build, follow its supplied installation instructions and runtime requirements. Keep the package complete, open the dashboard and verify one useful desktop widget before testing game features.
Make the first session a small one
Match the Windows, .NET Framework and Overwolf versions to the instructions for your complete build.
Open the dashboard and check one available PC control or reading. Add another only after the first behaves as expected.
If you need the Overlay, game FPS or capture, start the intended title and test that particular feature before an important session.
Repeat the same game scene with a small layout, then add Replay or other workloads individually. Choose the balance of controls and performance that works on your PC.
Your questions, answered
The current Overwolf package is for Windows 10 version 1809 or later, or Windows 11, with .NET Framework 4.8 and Overwolf Client 0.294.0.18 or newer. The bundled Windows native integration targets x64. Check the release channel and the requirements supplied with the exact build you receive.
No. Those are tools used to build the development package, rather than player requirements. A tester using a complete built package needs the supported Windows environment, .NET Framework runtime and Overwolf Client. Use the instructions provided for your distribution channel instead of installing development tools to troubleshoot a widget.
Desktop widgets can remain useful without a supported game. In-game Overlay, game FPS and capture have separate game and platform requirements. Check the exact game and edition against Overwolf's supported-games list, then verify the particular feature you need. Detection alone does not establish that every integration is available.
The Windows system integrations and current Overwolf package described here require Windows. Browser demonstrations can illustrate the interface on another device, but they do not provide the native controls or game Overlay. The phone companion is a browser control surface for a reachable Windows PC, rather than a console or macOS version of SysCubes.
No separate phone app is needed. Open its local page in the phone's browser and pair with the running Windows app on a trusted reachable network. PC Ethernet and phone Wi-Fi can work together when local communication is allowed. Available actions still depend on the PC's feature support and enabled companion modules.
SysCubes needs Windows 10 1809 or later, or Windows 11, with Overwolf. Beyond that, plan around your game's requirements and the widgets or capture you plan to use. Begin with a few useful widgets and compare the same scene before and after enabling capture or a larger layout.
Your PC. In your hands.
Explore SysCubes features, choose your screen layout, and download SysCubes for Windows free to install your desktop and in-game dashboard.
Free • No credit card or account needed • Instant 1-minute setup • Windows 10/11