Requirements and Supported Browsers

Pipe officially supports the following browsers.

Embed Code v2.0 #

💻 On Desktop Devices:

• Desktop recorder
  • webcam recording: Chrome 66+, Firefox 76+, Edge 79+ and Safari 14.1+^Beta on secure contexts (https, localhost, file://, etc.)
  • screen + camera recording: Chrome 74+, Firefox 76+, Edge 79+ and Safari 14.1+^Beta on secure contexts (https, localhost, file://, etc.)

📱 On Mobile Devices:

• Mobile native recorder:
  • Chrome on Android version 4.4 and up
  • Safari on iOS 6 and up
• Desktop HTML 5 recorder:
  • Chrome 66+ on secure contexts (https, localhost, file://, etc.) on Android
  • Safari on iOS/iPadOS 14.5+^Beta on secure contexts (https, localhost, file://, etc.)

Embed Code v1.0 #

💻 On Desktop Devices:

• Desktop recorder
  • webcam recording: Chrome 63+, Firefox 52+ and Edge 79+ on some secure contexts (https, localhost, 127.0.0.1 and ::1)
  • screen recording: Chrome 72+, Firefox 66+ and Edge 79+ on some secure contexts (https, localhost, 127.0.0.1 and ::1)

📱 On Mobile Devices:

• Mobile native recorder:
  • Chrome on Android version 4.4 and up
  • Safari on iOS 6 and up -Desktop HTML 5 recorder:
  • Not supported, use the 2.0 embed code instead

Secure Contexts #

Many web APIs and features- including those used to access a device’s camera and microphone - are accessible only in a secure context. That’s why our desktop recording client only works in secure contexts.

What Is a Secure Context? #

A web page is considered to be in a secure context if:

• it is served over https: the page is loaded via https://, ensuring data integrity and encryption.
• it is a local resource: origins such as http://localhost, http://127.0.0.1, file://, etc. are also deemed secure.

For a detailed explanation and list of secure contexts, refer to MDN’s article on Secure Contexts.

Testing on Insecure Contexts With Chrome #

Chrome has a flag that lets you force specific origins to be treated as secure: chrome://flags/#unsafely-treat-insecure-origin-as-secure . This can be used in development.

Recording Client Behaviour Over Insecure Contexts #

If the 2.0 desktop recording client is embedded in a non-secure context, it will display the following message, blocking functionality:

Recording is only possible over secure contexts (https, localhost, file://, etc.)

Here’s how the recording client shows the message: