Thinking of making the switch from CameraTag?

The Pipe HTML5 video recording client is just 75.4KB compressed, delivered over 4 HTTP requests. The CameraTag recorder is downloading 540KB over 10 http requests.

Because the Pipe desktop recorders begins streaming data back to our platform as soon as recording starts, there’s usually no need for an upload wait screen at the end.

With Pipe, if the user completely loses Internet connection, we recover the streamed data and process it as usual.

With Pipe, it is easy to configure the desktop recorder to record at 320p, 480p, 720p, or at any other resolution. CameraTag decides for you.

Our HTML5 recorder is fully TAB accessible. A must if you need to meet the double A WCAG accessibility rating for government websites.

Our HTML5 recorder, delivered via the new 2.0 embed code, uses only 5 HTTP requests to record. CameraTag requires double that.

We correctly process recordings up to 4k in resolution recorded from mobile devices.

The Pipe client supports 4 languages out of the box: English, French, German, and Spanish.

You can use Pipe to record both your user’s screen and camera using our built-in, extension-free screen and camera recorder. Works on Chrome, Firefox, and Safari.

Our new 2.0 JS embed code lets you easily add or remove recorders from your single-page apps with Angular, Vue, React, or plain JS.

Pipe can POST data to your server-side scripts at 6 points in the lifecycle of a recording, allowing for more granular integrations and immediate notifications.

Our private POST API lets you push recordings to the Pipe platform from any server-side code or mobile app, regardless of the technology. For more info, contact us.

Pipe’s account dashboard efficiently manages thousands of recordings. We show 50 recordings per page with in-depth info. These make it easy to spot problems or search on the page for specific recordings.

On the Pipe account dashboard, all dates and times are in your time zone (which you can change). Every recording and event is now easy to pinpoint in time. No more UTC guesswork.

With every recording, we collect additional metadata, including device names, audio/video codecs, sample rates, and channel count. This data gives you a clear picture of what’s coming in before transcoding.

If, for some reason, we are unable to push the recording and snapshot to your storage (for example, if your server is down for a while), we retry 12 times over 3 days (https://blog.addpipe.com/pipes-new-retry-mechanism-for-failed-attempts-at-copying-converting-or-storing/).

The success/error logs we keep for storage attempts are linked to each recording, searchable by recording ID, and can be filtered to show only problematic transfers.

At any time, you can cancel your subscription and/or delete your Pipe account, including all recordings and account data.