Theme Example is a reference implementation for creating custom themes for ownCloud Server. It demonstrates how to override the default branding -- including logos, colors, login page background, copyright text and other visual elements -- by providing a complete, working theme app that administrators can clone, customize and deploy on their ownCloud instances.
Note: This repository is in maintenance/legacy mode and is no longer actively developed.
This repository is part of the ownCloud Server (OC10) theming infrastructure. It provides a starting point for administrators and integrators who need to customize the look and feel of their ownCloud deployment.
Legacy notice: This repository is archived/legacy. For ownCloud Infinite Scale (oCIS), theming is handled differently through the web frontend configuration.
- Clone or download this repository to
owncloud/apps/:
cd apps
git clone https://github.com/owncloud/theme-example.git- Set proper permissions:
chown -R www-data:www-data theme-example- If you rename the app folder, update the
<id>inappinfo/info.xmlto match.
- Images: Open original images from
core/imgin an image editor, make changes, and overwrite the originals in the theme's directory. - Texts: Edit
defaults.phpto change copyright text, slogans and other display strings. - CSS: Modify
core/css/styles.cssfor visual customizations. Use browser developer tools (F12) to discover CSS classes.
Since theme files must be editable, the app is unsigned. Add to config/config.php:
'integrity.ignore.missing.app.signature' => [
'theme-example',
],Star this repo and Watch for release notifications!
We welcome contributions! Please read the Contributing Guidelines and our Code of Conduct before getting started.
- Rebase Early, Rebase Often! We use a rebase workflow. Always rebase on the target branch before submitting a PR.
- Dependabot: Automated dependency updates are managed via Dependabot. Review and merge dependency PRs promptly.
- Signed Commits: All commits must be PGP/GPG signed. See GitHub's signing guide.
- DCO Sign-off: Every commit must carry a
Signed-off-byline:git commit -s -S -m "your commit message" - GitHub Actions Policy: Workflows may only use actions that are (a) owned by
owncloud, (b) created by GitHub (actions/*), or (c) verified in the GitHub Marketplace.
Do not open a public GitHub issue for security vulnerabilities.
Report vulnerabilities at https://security.owncloud.com -- see SECURITY.md.
Bug bounty: YesWeHack ownCloud Program
This project is licensed under the AGPL-3.0.
The Kiteworks Open Source Program Office, operating under the ownCloud brand, launched on May 5, 2026, to steward the open source ecosystem around ownCloud's products. The OSPO ensures transparent governance, license compliance, community health, and sustainable collaboration between the open source community and Kiteworks, which acquired ownCloud in 2023.
- OSPO Home: https://kiteworks.com/opensource
- GitHub: https://github.com/owncloud
- ownCloud: https://owncloud.com
For questions about the OSPO or licensing, contact ospo@kiteworks.com.
The OSPO is driving a strategic relicensing of ownCloud repositories toward the Apache License 2.0, following the Apache Software Foundation's third-party license policy.
Individual repositories will migrate as their audit is completed. The LICENSE file in each repo reflects its current license status (not the target).
Current license: AGPL-3.0 (Category X per Apache policy -- cannot be included in Apache-2.0 works).
Migration prerequisites for this repository:
- CLA/DCO coverage: All past contributors must have signed agreements permitting relicensing
- Copyleft dependency audit: All AGPL/GPL dependencies must be replaced or isolated
- KDE heritage review: Any code with KDE-era copyrights requires legal analysis
- Complete relicensing: AGPL-3.0 is a strong copyleft license; migration requires full relicensing of all files, not just a header change