> For the complete documentation index, see [llms.txt](https://atlas.anywhere.now/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://atlas.anywhere.now/platform-administration/maintenance-mode-applications/snapper/configure-snapper-screen-recording.md). # Configure Snapper screen recording Configure Snapper screen recording storage and FFmpeg encoding. Configure Snapper screen recording when agents must record screen activity during incoming or outbound calls. {% hint style="warning" %} **Unsupported SharePoint uploads** Snapper reached End of Support Maintenance (EoSM) in October 2023. Snapper screen recording does not support Microsoft Entra ID app + certificate authentication for SharePoint connections. Microsoft retired legacy Client ID/Secret authentication in April 2026. Therefore, affected Snapper-to-SharePoint upload scenarios are not supported. Because Call Property Service is being deprecated alongside Snapper, screen recording links should no longer be expected to appear in the contact timeline, reporting data, or contact center history. {% endhint %} ## Before you begin Make sure: * Screen recording is allowed for the customer environment. * The target local path is available. * Secrets, usernames, app IDs, tenant URLs, and customer-specific prefixes are handled through the customer's secure process. ## Configure storage settings Use one setting per row when preparing a configuration package. | Setting | Value | Default | Description | | ------------------------------------------ | ------------------ | --------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Automatic screen recording incoming calls | on/off | off | Activate screen recording for incoming calls. | | Automatic screen recording outbound calls | on/off | off | Activate screen recording for outbound calls. | | Automatic save screen recording to | Local / SharePoint | Local | Select where Snapper stores screen recording `.mp4` files. | | Screen selection | Dropdown | Primary | Select the screen to record. | | Local save path | Text | `c:\snapper_screencaptures` | Store local screen recordings and local cache during recording. | | SharePoint Location | Onpremise / Online | Onpremise | Select SharePoint Server or SharePoint in Microsoft 365. **Note: No longer possible after April 2026.** | | SharePoint URL | Text | Empty | SharePoint UCC site URL. Files were written to `InboundScreenRecordings` or `OutboundScreenRecordings`. **Note: No longer possible after April 2026.** | | SharePoint Username | Text | Empty | Domain/username or UPN used for SharePoint. **Note: No longer possible after April 2026.** | | SharePoint Password | Hidden text | Empty | Password for the username. **Note: No longer possible after April 2026.** | | SharePoint App Id | Text | Empty | App ID of an Online app capable of creating and writing to the SharePoint library. **Note: No longer possible after April 2026.** | | SharePoint App Secret | Hidden text | Empty | Client secret of an Online app capable of writing to the SharePoint site. **Note: No longer possible after April 2026.** | | Save SharePoint upload URL to UCC database | on/off | off | Add the screen recording URL to the CDR database so it appears in reports. Because Call Property Service is being deprecated alongside Snapper, screen recording links should no longer be expected to appear in the contact timeline, reporting data, or contact center history. **Note: No longer possible after April 2026.** | | Enable Prefix Filter | on/off | off | Turn on prefix filtering. | | Prefix | Text | Empty | Part of the URI to filter on. Example: `ucc_`. | {% hint style="warning" %} Do not enter or share tenant-specific URLs, app IDs, usernames, passwords, app secrets, or customer-specific prefixes outside the customer's secure process. {% endhint %} ## Install FFmpeg FFmpeg is required for screen recording encoding. 1. Download `ffmpeg-master-latest-win64-gpl.zip` from: ``` https://github.com/BtbN/FFmpeg-Builds/releases ``` 2. Extract the `.zip` file to a temporary location. Unblock the downloaded `.zip` file first if needed. 3. Locate `FFMpeg.exe` in the extracted folder, typically under `...\bin`. 4. Copy `FFMpeg.exe` to the Snapper installation directory: * 32-bit example: `C:\Program Files (x86)\Anywhere365 Snapper\` * 64-bit example: `C:\Program Files\Anywhere365 Snapper\` 5. Delete temporary extraction files if they are no longer needed. ## Recording output Snapper uses FFmpeg to encode screen recordings with these specifications: | Encoder | File extension | Video codec | Audio codec | FPS | | ------- | -------------- | -------------------------- | -------------------------- | --- | | FFmpeg | mp4 | Advanced Video Codec (AVC) | Advanced Audio Codec (AAC) | 10 | VLC Player is one possible playback application for the generated files. ## Verify screen recording 1. Start Snapper with a test user. 2. Place a test call in a configuration where screen recording is enabled. 3. Confirm that the `.mp4` file is created locally. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://atlas.anywhere.now/platform-administration/maintenance-mode-applications/snapper/configure-snapper-screen-recording.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.