We fixed a Safari-specific issue where enabling the real-time background blurring effect would result in a “double-image” effect instead of a properly blurred background.
Build slug: 31b7f3c81
Every update to the Pipe platform: new features, improvements and fixes.
We fixed a Safari-specific issue where enabling the real-time background blurring effect would result in a “double-image” effect instead of a properly blurred background.
Build slug: 31b7f3c81
We fixed a bug where starting a new recording while a video was playing back would leave the preview video in the bottom-right minified position. The video preview now correctly returns to its original, full-size position when a new recording is started during playback.
Build slug: 3a472ceac
We fixed several Safari-specific UI issues in the recording client. Icons in the bottom menu are no longer cut off, and hover interactions have been fixed to prevent icons from twitching or shifting unexpectedly.
Build slug: b8ae38714
We fixed an issue in Safari on iOS and macOS where video recordings used a hardcoded bitrate of 5Mbps regardless of resolution. This limited video quality when recording at high resolutions. The recording client now applies resolution-appropriate bitrates, ranging from 0.3 Mbps for 240p up to 14 Mbps for 4K recordings. We’ve also updated the documentation to include these bitrates.
Build slug: 4df062d59
<button> element to a <div> element. This change aligns it with the rest of the recording client buttons, which are all implemented as <div> elements .Build slug: 7c845b616
Build slug: 70097637a
We fixed an issue where triggering the recording start action multiple times simultaneously via the JavaScript Control API would result in the recording data being written multiple times to the same file. The recording client now ensures that a recording starts only once.
Build slug: c5bbaa28b
We improved playback stability by adding checks that prevent overlapping play and pause calls, avoiding the DOMException: The play() request was interrupted error.
We fixed an issue where screen recording did not work correctly when the audio-only (pipe-ao) embed code option was enabled.
Build slug: e835f9d2e
pipe.css network requests made by the recording client.We introduced a new embed option, loglevel, that hides all console logs when set to 1.
Build slug: 41271e501
Build slug: 875895486
The microphone input checks that can trigger the “Your microphone might be muted by your system settings.” warning now use a finer measurement value. This results in more accurate detection of low-level audio input.
Build slug: 23cb53c39
The recording client now performs microphone input checks more efficiently.
Build slug: fa8ed68e4
The recording client now correctly handles a new EncodingError message (“The given encoder configuration is not supported by the encoder.”), restoring the fallback behavior on older Android devices. Previously, the monitored message was “Video encoding failed”.
Added a new embed code option called disableaudiowarningmsg to hide the warning message displayed at the bottom of the recording client when no audio is detected.
Video quality on Safari: Switched to a variable video bitrate for MP4 video recordings (Safari on iOS and macOS) for better video quality. The requested bitrate now ranges from 0.3Mbps for 320x240 to 14Mbps for 4k recordings (instead of defaulting to 2.5Mbps).
^le: A separate 5Mbps limit remained in place until we removed it in this build.
Microphone Input Warning: Switched to checks every 1 second (instead of 2) when we detect a microphone with no input. We mark an input device as having sound right away (without waiting for 15 seconds as in the initial implementation).
Build slug: fd21de285
The 2.0 recording client now fully supports versioned builds, allowing you to lock your integration to a specific version.
For full details on how versioning works, selecting a version, and best practices, please refer to our documentation.
Below are the currently available builds, along with their build slugs and release dates:
2599b99ea - 2025-11-13 - View changelog (latest build published 6 days ago)9249ecb2d - 2025-11-11 - View changelog2706f69e8 - 2025-11-06 - View changelogThe recording client now features improved icons for a cleaner and more consistent interface.
Build slug: 2599b99ea
Our main audio, video and screen recording client now plays back recordings directly from a local in-memory blob, eliminating the need to fetch files from the ingestion server over HTTPS. This is how the existing download function works. This improvement enables instant playback and seeking. The improvement will be visible especially to users on slow or unstable connections like mobile connections.
Build slug: 9249ecb2d
When recording screens with very high resolutions (above 4K), some browsers could trigger an EncodingError, preventing the recording from starting.
The recording client now includes a fallback mechanism: if an EncodingError occurs during screen recording initialization, it will automatically retry using the VP8 codec and attempt to restart the recording instantly.
Build slug: 2706f69e8
We’ve implemented new changes to the account dashboard:
We’ve made the following improvements to the account dashboard:
We’ve implemented a new concurrency limit mechanism that activates ONLY when a processing server hits a certain threshold considered a high load.
The concurrency limit means only a specified number of recordings may be processed at a time per account by our processing servers. Each account has a concurrency limit value based on the account type:
1 maximum number of concurrent recordings processed during load2 maximum number of concurrent recordings processed during load4 maximum number of concurrent recordings processed during loadThe above limits will be enforced when more than half of the available processing workers on the server are in use at any given moment. Otherwise, the per-account limits are ignored, and accounts can ‘burst’ and use more workers than their limit allows for recording processing.
The recordings list in the Pipe account dashboard now displays rotation information for all recordings, including those made from mobile devices through streaming - they carry rotation information too - and those made natively on mobile devices but uploaded from a desktop device.
Our recording client is now fully accessible via keyboard navigation. All interactive elements can be reached and operated using standard keyboard controls, improving accessibility for end users.
Fixed an issue on Safari where starting a screen recording could fail with the error message InvalidStateError occurred.
Added support for screen recording without microphone or microphone access.
When screen sharing, you’ll now choose the screen sharing surface 1st and then you’ll be asked for microphone access.
Two important updates to our recording client when used for screen sharing & recording:
For more information, please refer to this blog post.