> For the complete documentation index, see [llms.txt](https://docs.arcade.software/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.arcade.software/kb/build/brand-kits-and-themes/share-page-themes.md). # Share Page Themes ### What is a Share Page theme? A Share Page theme is a reusable design preset that controls what viewers see when they visit the share page for any of your content. Share pages are shared across demos, videos, and collections, so share page settings are managed separately from Demo themes. Share Page themes live inside Brand Kit under Settings → Brand Kits → Themes → Share Page. ### What is the difference between a Share Page theme, a Demo theme, and per-Arcade Branding? Share Page theme is a reusable preset that controls what viewers see on your share page — logo, favicon, CTA button, and watermark. Because share pages are used across demos, videos, and collections, these settings are managed independently from demo settings. Demo theme is a separate reusable preset that controls how your interactive demos look and behave — fonts, backgrounds, cursors, navigation, and so on. Per-Arcade Branding is for one-off overrides on a single Arcade. If you need a specific logo, favicon, or CTA for one Arcade without touching your workspace settings, that is what branding is for. ### How do I access Share Page themes? Open a Brand Kit from Settings → Brand Kits, then navigate to Themes in the left-hand sidebar and select the Share Page tab. You can also select your Share Page theme directly from the Preview page of any Arcade. ### What can I customize in a Share Page theme? * Logo — Appears in the header of your share page, with an optional link URL * Favicon — Browser tab icon * CTA button — Custom call-to-action text and destination URL * Watermark — Show or hide the Arcade watermark, or add your own (plan-dependent) ### Can I move Share Page themes between Brand Kits? Yes. You can move a theme to a different Brand Kit using the move to option, similar to how you move Arcades between folders. This is useful if you have many themes — for example, themes built for different sub-brands — and want to organize them under the appropriate Brand Kit. ### Are Share Page themes and Demo themes completely separate? Yes — they are fully isolated. Creating a new Share Page theme does not create a matching Demo theme, and vice versa. If you delete a Share Page theme, the Demo theme with the same name is unaffected, and vice versa. The only time they share names is right after migration, when each existing theme is duplicated into both a Share Page version and a Demo version. Any themes you create going forward are built specifically for one or the other. ### Who can edit Share Page themes? Only workspace admins can edit theme settings. ### What do Free accounts get? Free accounts have a default Arcade Share Page theme applied automatically but cannot edit theme settings. Theme settings are still applied — they are just not customizable until you upgrade. ### What happened to the standalone Themes page? The Settings → Themes page no longer exists. Visiting the old link automatically redirects you to Brand Kit. All theme management now lives under Settings → Brand Kits. ### What happened to my existing themes after the migration? Nothing was lost. Your themes were migrated automatically: * Each existing theme was split into a Share Page theme and a Demo theme. For example, "Marketing" became "Marketing Share Page" and "Marketing Demo." * All themes moved under your first Brand Kit by default. Your live share pages look and work exactly as before — only the location of the settings changed. If you would like your themes reorganized under a different Brand Kit, use the move to option or contact support. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.arcade.software/kb/build/brand-kits-and-themes/share-page-themes.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.