> For the complete documentation index, see [llms.txt](https://docs.uxwizz.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uxwizz.com/installation/requirements/limitations.md).

# Limitations

Check the behavior you need on a representative page before enabling tracking across a site. Recording mode, privacy settings, browser restrictions, and server capacity all affect the result.

## Recording and session playback

**Default page recording** stores actions and page URLs. Playback loads the current website, so changes to the page, login requirements, and iframe restrictions can affect what you see. Replayed actions can run on the live page. Add the `UST_noClick` class to controls that must not be clicked during basic replay, such as a final order button:

```html
<button class="UST_noClick" type="submit">Place order</button>
```

Keep any existing classes. The basic replay still shows the click but does not dispatch it to that element or its descendants. This does not mask the element or stop real visitors from using it. Verify the behavior on a test page before replaying sensitive actions.

**Full page recording** captures page content and changes. It is better suited to dynamic pages and content behind a login, but it does not guarantee that every browser feature can be reproduced. Blocked assets, privacy masking, canvas settings, and unsupported embedded content can affect the result.

Cross-origin iframe recording requires the appropriate tracking configuration and cooperation from the embedded page. Installing a tracker only on the parent page does not give it unrestricted access to another origin's content. Test the exact iframe integration you use.

See [Recording modes](/api/session-recording.md) and [Masking or ignoring elements](/api/session-recording/ignore-specific-elements.md).

## Heatmaps

* **Live page** uses the current website and can be blocked by its frame policy.
* **Recorded snapshot** needs compatible full-recording content for the selected page and screen size. **Auto** can use an available snapshot when the live page cannot load.
* Heatmap points describe interaction positions. A popup, dropdown, or changed layout can place those points over content that was not visible during the original visit.
* Compare similar page layouts and screen sizes before interpreting differences.

If the background is missing, follow the [iframe troubleshooting guide](/guides/troubleshooting/dashboard/website-iframe-not-loading-x-frame-options.md).

## Storage and performance

There is no single server size that guarantees a particular monthly traffic volume. Full recordings, long sessions, large pages, canvas capture, and retention periods can greatly change storage needs.

Use the [server sizing guide](/installation/requirements/server-specs-cpu-ram.md), monitor actual usage, and configure [retention](/installation/optimization-tips/auto-delete-old-data-cron-jobs.md). Leave free disk space for database operations, updates, and backups.