Skip to main content

App Signing for Production

Sign your app with @overwolf/ow-electron-builder so the gaming packages (GEP, Overlay, Recorder) load at runtime once the app is distributed to users.

For running gaming packages locally before signing, see Dev Mode.

PropertyValue
SurfaceOverwolf Electron (ow-electron)
Minimum version@overwolf/ow-electron-builder 26.9.0
PlatformWindows
When to useBuilding a production app for distribution
Your certificateA code-signing certificate for your exe (your own certificate, not Overwolf's). See code signing.
warning

Code-signing your exe with your own certificate is now required (previously optional). Overwolf signs the gaming package integrity and you sign the exe. Without both, the gaming packages (GEP, Overlay, Recorder) will not load at runtime.

Signing credentials and variables​

VariablePurposeSource
OW_CLI_EMAILSigning server authenticationYour Overwolf Console account email
OW_CLI_API_KEYSigning server authenticationOverwolf Console, under Profile > API Keys
OW_BUILD_KEYSigning server authentication for the build stepOverwolf Console, under Release management > App Keys

Prerequisites​

Before you sign, you need:

  1. A registered app in the Overwolf Console with an assigned App UID.
  2. A valid OW_CLI_EMAIL and OW_CLI_API_KEY for an account that owns the app.
  3. An OW_BUILD_KEY from the Overwolf Console, for the build step.
  4. A code-signing certificate for your exe (your own certificate, not Overwolf's). See code signing.
  5. @overwolf/ow-electron-builder installed.

Step 1: Set signing credentials​

Provide the required signing credentials as environment variables:

export OW_CLI_EMAIL=your-email@example.com
export OW_CLI_API_KEY=your-api-key
export OW_BUILD_KEY=your-build-key

Step 2: Run the builder​

Build and sign your app with a single command:

npx @overwolf/ow-electron-builder