---
title: "Replace the Keep Logo with a Custom Logo for White Labeling"
slug: "replace-the-keep-logo-with-a-custom-logo-for-white-labeling"
description: "White-label Keep by replacing the default Lasernet logo in the header with your own, for both light and dark mode."
updated: 2026-10-05T15:01:02Z
published: 2026-10-05T15:01:02Z
canonical: "kb.lasernetgroup.com/replace-the-keep-logo-with-a-custom-logo-for-white-labeling"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://kb.lasernetgroup.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Replace the Keep Logo with a Custom Logo for White Labeling

You can rebrand Keep by replacing the default Lasernet logo. Your new logo will appear on the login page and in the corner of all other pages. You can use separate logo files for light and dark mode.

## Add Your Logo Files

1. Prepare logo files for light mode and dark mode. SVG is recommended because it scales easily, allowing you to use a smaller filesize; PNG, JPEG, GIF, WebP, and AVIF are also supported.
2. Store both files in the top-level Keep installation folder, for example `C:\Program Files\Lasernet\Lasernet Keep\Server_11.3 - myserver`. Storing them with the installation helps make sure the Keep service can read them. In a clustered installation, store the files at the same path on every node.
3. In the Branding section of `node.properties`, remove the hash mark (`#`) at the start of the `app.branding.logo.light.path` and `app.branding.logo.dark.path` lines. Set each property to the path of the matching file:

```plaintext
# Branding
# --------------------------------------------------

app.branding.logo.light.path=C:/Program Files/Lasernet/Lasernet Keep/Server_11.3 - myserver/customer-logo-light.svg
app.branding.logo.dark.path=C:/Program Files/Lasernet/Lasernet Keep/Server_11.3 - myserver/customer-logo-dark.svg
```

> [!NOTE]
> Note
> 
> Branding is disabled by default, because both properties are commented out with a hash mark (`#`). Remove the `#` from both lines to enable it. If you copy a file path from Windows Explorer, note that `node.properties` uses the backslash character (`\`) to mark a line continuation. When you set the file path, either escape each backslash by typing `\\`, or use the forward slash (`/`) instead. For general instructions on locating and editing `node.properties`, see [Set Configuration Flag Values in node.properties](/v1/docs/set-configuration-flag-values-in-nodeproperties-1).
4. Save `node.properties`, then restart the relevant Keep node's Windows service.
5. Reload Keep in your browser to display the new branding.

## If Your Logo Does Not Appear

- Both properties must point to a valid, readable file. Keep never mixes a custom logo with the standard one. If either property is unset or points to a file that does not exist or that Keep cannot read, Keep uses its standard branding in both light and dark modes.
- In a clustered installation, check every node. The configured files must exist at the same path on each one.