# Clip History Not Showing

You copied something but **it doesn't appear in Octoclip's clip history**. Work this page. This is a capture-layer problem: first confirm whether the content **was recorded at all** — if it wasn't, other devices can't receive it either, so don't change the sync method first.

Not sure this is the right page? Use the minimal test in the [Troubleshooting overview](/advanced/troubleshooting/overview) to find the layer first.

## Who this is for

- Users who can't find a copy in the local clip history
- Users who can't receive content across devices and haven't confirmed whether the source recorded it

If the history **has the record and only another device can't receive it**, see [Sync Failed](/advanced/troubleshooting/sync-failed). If it's recorded "sometimes" or stops after the screen locks, see [Background Monitoring Unstable](/advanced/troubleshooting/background-monitoring-unstable).

## Run one minimal test

```text title="Minimal test text" noLineNumbers
octoclip-history-001
```

Copy it, then immediately open Octoclip's clip history to see whether it appears.

## Check in order

:::steps
:::step{title="Confirm the app is running and monitoring isn't paused"}

Make sure Octoclip is running (desktop stays in the tray/menu bar) and clipboard monitoring isn't manually paused.

:::
:::step{title="Confirm the clip source is enabled"}

Confirm the source you expect (system clipboard, system share, screenshots, etc.) is on. See [Clip Sources Overview](/features/source/overview).

:::
:::step{title="On mobile, confirm background monitoring"}

When clipboard background monitoring is off or not working, you often have to **open the app before copying** for it to be recorded. See [Clipboard background monitoring](/features/source/background-monitoring/) and [Quick start](/features/source/background-monitoring/quick-start).

:::
:::step{title="Relax battery and background restrictions"}

System battery policies may kill the background service so copies aren't recorded. Allow Octoclip to run in the background while testing.

:::
:::step{title="Check filter rules"}

Confirm the copied content didn't match a history filter rule you set. See [History filter rules](/features/clip-history/filter-rules).

:::
:::step{title="Test with plain text first"}

Test with the short text above first, then images, files, or codes, to tell "records nothing" apart from "doesn't record a certain type."
:::
:::

> [!NOTE] Desktop and mobile behave differently
> On desktop under a normal install, fewer restrictions apply to recording clips than on mobile. Whether mobile can record reliably **without opening the app** depends on background monitoring availability and system policy. See [Recording expectations](/getting-started/clipboard-record-expectations).

## How to verify after fixing

- Copy `octoclip-history-001`.
- See the text at the top of the clip history list immediately.
- Copy an image or link too, and confirm that content type is recorded.

## Still not solved

Please include:

- Platform and OS version
- App version
- Symptom (records nothing / a certain type isn't recorded / intermittent)
- Content type (plain text / link / image / file reference)
- Whether the relevant clip source and background monitoring are enabled
- Whether you set any history filter rules
- Reproduction steps (shortest path)

## Next steps

:::cards{cols=2}
:::card{title="Recording expectations" icon="lucide.clipboard-list" href="/getting-started/clipboard-record-expectations"}
Set expectations for "when content should appear in history" to reduce misdiagnosis.

:::
:::card{title="Clipboard background monitoring" icon="lucide.monitor-cog" href="/features/source/background-monitoring/"}
Understand background monitoring and how to enable it per platform.

:::
:::card{title="Background monitoring unstable" icon="lucide.activity" href="/advanced/troubleshooting/background-monitoring-unstable"}
If it's "recorded sometimes," debug background stability separately.

:::
:::card{title="Sync failed" icon="lucide.refresh-cw" href="/advanced/troubleshooting/sync-failed"}
If the local device records but another device can't receive, move to sync debugging.
:::
:::