> For the complete documentation index, see [llms.txt](https://wiki.crosswatch.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.crosswatch.app/crosswatch/settings/ui-settings/user-interface.md). # User interface Choose which dashboard elements stay visible and how CrossWatch serves the UI. Most changes apply after you click **Save**. Theme and visibility changes apply immediately. Protocol and TLS changes need a restart. ### Visibility

User interface visibility settings for widgets, Recent Activity, and Quick Add.

These controls only change the UI. They do not change sync, scrobble, or provider behavior. #### Watchlist Show or hide the Watchlist widget on the **Main** page. This widget shows recently added active watchlist items. A TMDb API key is required. CrossWatch hides this widget when TMDb is not configured. #### Recent history widget Show or hide the **Recent History** widget on the **Main** page. This widget shows the latest watched movies, shows, seasons, and episodes known to CrossWatch. #### Latest ratings widget Show or hide the **Latest Ratings** widget on the **Main** page. This widget shows the most recent ratings known to CrossWatch. #### Recent Scrobble widget Show or hide the **Recent Scrobble** widget on the **Main** page. This widget shows successful scrobble and watched activity with artwork, media details, and provider route icons. This is separate from **Recent Activity**. Hiding this widget does not hide the text-based **Recent Activity** list. #### Playing card Show or hide the footer **Now Playing** card. This does not disable Watcher or playback tracking. #### Recent activity Show or hide the text-based **Recent Activity** list on the main dashboard. Hiding it does not stop local activity logging. #### Recent activity display Choose how much Recent Activity the main dashboard shows. Options: * `Last 3 items` * `Last 4 items` * `Last 5 items` * `Last 24 hours, max 5` * `Last 48 hours, max 5` * `Last 72 hours, max 5` Default: * `Last 3 items` Guide: [Recent Activity](/crosswatch/settings/scrobbler/recent-activity.md) #### Dashboard widget defaults All four media widgets are shown by default unless you disable them. Changes apply after you click **Save**. CrossWatch does not need a restart. These controls map to: * `ui.show_watchlist_preview` * `ui.show_recent_history_widget` * `ui.show_latest_ratings_widget` * `ui.show_recent_scrobble_widget` Guide: [Dashboard widgets](/crosswatch/main-dashboard/dashboard-widgets.md) #### Recent syncs display Choose how many recent sync items the dashboard shows. #### Desktop Quick Add Show or hide the desktop Quick Add entry in the UI. #### Mobile Quick Add Show or hide the mobile Quick Add entry in the UI. ### Theme

Theme settings for the CrossWatch web interface.

#### Theme Choose the theme for the full web interface. Theme changes affect presentation only. They do not change sync settings or provider behavior. Options: * `Flat dark` — default theme with dark backgrounds, flat panels, reduced effects, and clear contrast * `Flat light` — light version of the flat theme with light backgrounds, dark text, and adjusted borders and status colors * `Original` — restores the classic CrossWatch look and removes the flat-theme styling layer To change the theme: 1. Open **Settings**. 2. Open **UI settings → User interface**. 3. Locate **Theme**. 4. Choose `Flat dark`, `Flat light`, or `Original`. 5. Click **Save**. The selected theme applies immediately. No page reload or CrossWatch restart is required. CrossWatch also stores the current selection in the browser. This keeps the same theme active when you open the page again. Clicking **Save** writes the value to `ui.theme` in the CrossWatch configuration. On startup, CrossWatch applies the stored theme before the main UI finishes loading. This reduces visible theme switching while the page opens. Missing or unsupported values fall back to `Flat dark`. ### Protocol

Protocol and TLS settings for serving the CrossWatch web UI.

#### UI protocol Choose how CrossWatch serves the web app. * `HTTP` — best when a reverse proxy already handles HTTPS * `HTTPS (self-signed)` — CrossWatch serves HTTPS directly with its own certificate {% hint style="warning" %} If you switch between HTTP and HTTPS, update any webhook or callback URL that points to CrossWatch. {% endhint %} ### TLS controls Use **Advanced** next to the protocol setting for certificate controls. That includes: * self-signed vs custom certificate mode * hostname and SAN values * cert and key file paths * certificate download and regeneration * path validation and TLS status Restart CrossWatch after changing protocol, certificate mode, hostname, SANs, or cert paths. {% hint style="info" %} Use [HTTPS/TLS](/crosswatch/advanced-and-api/https-and-tls.md) for the full TLS guide, including certificate trust, reverse proxy setup, and troubleshooting. {% endhint %} ### Related topics * [Main dashboard](/crosswatch/main-dashboard.md) * [Navigation](/crosswatch/main-dashboard/navigation.md) * [Dashboard widgets](/crosswatch/main-dashboard/dashboard-widgets.md) * [Recent Activity](/crosswatch/settings/scrobbler/recent-activity.md) * [Quick Add](/crosswatch/main-dashboard/navigation/quick-add.md) * [HTTPS/TLS](/crosswatch/advanced-and-api/https-and-tls.md) --- # 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://wiki.crosswatch.app/crosswatch/settings/ui-settings/user-interface.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.