Updated: 8 October 2026 · Applies to: Centova Cast v3 (3.3.4, from Centova documentation); file commands and the postupdate script tested on Debian 13 (coreutils 9.7, file 5.46)
According to Centova, the Centova Cast logos are plain PNG files in /usr/local/centovacast/web/theme/images/ on the server. Replace logo.png to change the logo in the client, reseller and admin areas, and login-logo.png to change the logo on the login page. This needs root access. Resellers without root access can instead upload their own logo on the Reseller Options tab of their settings, and their clients then see that logo in their control panels.
Which option is yours
- Stream owners (one radio station on shared Shoutcast and Icecast hosting): the panel logo is set by the server owner or your reseller, so there is nothing to change on your side.
- Resellers (for example our white-label Shoutcast reseller hosting): use the reseller logo setting below.
- Server owners with root access (for example a Centova Cast dedicated server): replace the PNG files as shown further down.
Reseller: upload your logo in the panel
- Log in to your Centova Cast reseller account.
- Open your account's Settings page and go to the Reseller Options tab.
- Under Branding, upload your image in the Logo image field and save. According to Centova, this logo is shown in your clients' control panels instead of the logo of your provider.
- Log in to one of your client accounts to check it. The same tab also has the Sender E-mail address used on notification emails.
Centova documents this setting for your clients' control panels only; it does not mention the login page. Centova does not list a size limit either, so use a small, wide image of about the same shape as the logo you see in the panel now.
Server owner: replace the logo files (root)
- Log in over SSH as root, go to the images folder and check the size of the current files, so your logo can match them:
cd /usr/local/centovacast/web/theme/images/ file logo.png login-logo.png logobar-bg.png
fileprints the width and height of each image. One of our test files, for example, showedlogo.png: PNG image data, 200 x 50, 8-bit/color RGB, non-interlaced. Your sizes will be different. - Back up the originals:
cp -p logo.png logo.png.orig cp -p login-logo.png login-logo.png.orig
- Upload your logos as PNG files at the same sizes (for example with SFTP to
/root/) and copy them over the originals:cp /root/my-logo.png /usr/local/centovacast/web/theme/images/logo.png cp /root/my-login-logo.png /usr/local/centovacast/web/theme/images/login-logo.png
Copying over an existing file keeps that file's owner and permissions. In our test, files owned by thecentovacastuser with mode 644 kept that owner and mode after root copied new images over them. - If you want to keep the existing header background behind your logo, Centova suggests using
logobar-bg.pngfrom the same folder as the background of your logo image. - Open the panel and reload the page without the browser cache (or use a private window), because browsers keep old images for a while.
To undo the change, copy the backup back: cp logo.png.orig logo.png.
Keep your logo after Centova Cast updates
According to Centova, updates overwrite modified image and CSS files, so the stock logos come back after an update. Centova Cast runs /usr/local/centovacast/sbin/postupdate after every update if that file exists and is executable. Keep your logos in a folder of your own and let that script copy them back:
mkdir -p /root/centova-branding cp /root/my-logo.png /root/centova-branding/logo.png cp /root/my-login-logo.png /root/centova-branding/login-logo.png
Create /usr/local/centovacast/sbin/postupdate with this content:
#!/bin/sh
# Put our own logos back after every Centova Cast update
cp -f /root/centova-branding/logo.png \
/root/centova-branding/login-logo.png \
/usr/local/centovacast/web/theme/images/
Then make it executable:
chmod 755 /usr/local/centovacast/sbin/postupdate
We tested this by putting the stock files back (as an update would) and running the script: it returned 0 and the checksums of both logos matched the copies in /root/centova-branding again. Centova's own example uses a preupdate script to save the files before the update and postupdate to restore them; keeping a permanent copy, as above, does the same job with one script. See the Centova update command for running updates.
More than a logo
For colours, layout and the login page design, see Can the Centova Cast web interface be rebranded? and How do I rebrand or customise the Centova Cast web interface?. On a dedicated server you can do all of this yourself with root access, or ask our engineers to do it as a paid task through Hire an Expert.
Official documentation: Centova: How do I apply my own logo to Centova Cast?, Centova: Reseller Options, Centova: Update Utility (preupdate and postupdate).
