This article details viewer requirements for Vidyard videos. It includes information about compatibility with most major browsers and operating systems (including mobile OS), support for autoplay, as well as support for events/CTAs on mobile.
Playback requirements
At Vidyard, we endeavour to guarantee full functionality for the Vidyard Player across all modern HTML5 browsers. In supported browsers, the Vidyard player operates using TLS 1.2 security protocol and HLS technology to deliver video content in H.264/AAC.
For outdated browsers that do not meet the standards required to support the Vidyard Player, we’ve created a legacy player that will continue to allow playback but may not include all the extra bells and whistles. This ensures that your videos will still play, while allowing Vidyard to continue to develop using the most recent technologies available.
Tip: It’s important to keep your browser as up to date as possible. Vidyard works hard to guarantee support across different iterations of browsers, but ongoing browser updates may affect our support for older browser versions.
Supported browsers
Browser | Version |
---|---|
Google Chrome |
Current, Current -1 |
Firefox |
Current, Current -1 |
Safari |
Current |
Microsoft Edge |
Current |
Internet Explorer |
v11 |
Opera |
Current, Current -1 |
Limited-support browsers/OS
Internet Explorer
For both Internet Explorer v9 & 10, Vidyard will continue to serve video content through our legacy player.
The legacy player is designed to allow playback, but may not guarantee much of the functionality expected from the Vidyard player in supported browsers (Events and CTAs, analytics, etc.). The legacy player no longer receives time or resources for active development, testing, or bug fixes.
Any changes that may occur to IE v9 & 10 may therefore cause player performance or features to fail or perform poorly. At this point, player functionality and features are offered as a "best effort".
Internet Explorer v7 & 8 are strictly not supported. This includes circumstances where a more recent browser (such as IE11) may be attempting to view the Vidyard Player on a webpage in compatibility mode.
Browser | Version | Level of support |
Internet Explorer | v9 & 10 | Uses legacy player |
Internet Explorer | v7 & 8 | Not supported |
A note about Windows support
Due to a limitation of the Windows 7 operating system, viewers attempting to play HLS video content using Internet Explorer 11 will be served a modified version of the Vidyard Player.
This player offers all regular player functionality except for resolution options, playback speed, and multi-track audio controls.
Players created from YouTube
Players created in Vidyard using the Add from YouTube option are subject to the browser compatibility and limitations of YouTube's player. Verify that your browser is compatible with Youtube.
Supported mobile OS/device
*Assuming only major browsers on these platforms (for example, Chrome on Android devices, Safari on iOS).
Operating System | Version |
---|---|
Android |
v4.4+ |
iOS |
v7+ |
Autoplay by OS/browser
Shortly after video became supported on mobile devices, muted autoplay was imposed as a restriction on mobile platforms in the interest of conserving battery life, preventing unwanted data usage, and to improve the overall user experience.
With the introduction of Chrome v66, Google has further extended muted autoplay to desktop browsers with changes to the way Chrome handles video, GIFs and other rich media.
Much like Apple’s policy introduced with Safari v11, Chrome now only allows muted autoplay. Users must perform a gesture ( e.g. click, swipe) to enable audio or pass a certain threshold on the Media Engagement Index (MEI) to allow video content from a particular website or domain to autoplay with sound.
As major internet browsers continue to move toward further restrictions on autoplay and enable users greater control over how they experience media content on the web, there are some general notes to keep in mind:
- These changes affect all kinds of video players and visual media on the internet (YouTube, Vimeo, etc.), including the Vidyard player.
- Browsers have implement these new behaviors to provide users with greater control over how they consume media. Ideally, it also improves the quality of clicks, impressions, and views that publishers receive from their content.
- Muted autoplay helps to further unify the web experience between desktop and mobile.
Browser/OS | Autoplay rules |
---|---|
Desktop |
|
Chrome |
Videos with autoplay are muted. Autoplay with audio is allowed if threshold on MEI passed. |
Firefox |
Autoplay with audio is allowed. |
Safari |
Videos with autoplay are muted. You may whitelist websites to autoplay media in the Safari preferences “Websites” tab. |
Edge |
Autoplay with audio is allowed. |
Internet Explorer |
Autoplay with audio is allowed. |
Mobile |
|
Android |
Videos with autoplay are muted. Autoplay occurs when media enters the viewport. |
iOS |
Allows muted autoplay with <playsinline> element. Autoplay occurs when media enters the viewport. |
Autoplay and GoVideo
Restrictions to autoplay pose a particular challenge to GoVideo users who share their recordings via email.
In addition to clicking on the video thumbnail in the email to load the sharing page, individuals who receive a GoVideo recording may also have to click again to unmute the video after it fails to autoplay with sound.
We think this creates a poor experience for GoVideo users and their audiences.
As a solution, we’ve implemented the autoplay=2
query string. Autoplay=2
allows the player to detect whether the browser will mute the video. If the browser will allow autoplay with sound, autoplay will proceed. Otherwise, the video thumbnail will display instead.
Autoplay=2
is applied by default to GoVideo recordings that have been configured to use autoplay.
Vidyard Event & CTA compatibility on mobile
Depending on the mobile operating system, Vidyard events (such as email gates, annotations, CTAs, etc.) may not be compatibility with viewer's mobile devices.
Most notably, Apple iOS did not support use of the <playsinline>
element prior to iOS v10. This element is required to watch videos outside of fullscreen mode. The same <playsinline>
element now allows viewers to see events that have been added to videos when playing inline.
OS | Fullscreen events (includes Marketo forms) | Annotations |
---|---|---|
iOS (v10+) |
iOS supports the use of pre-roll and post-roll events.
The video must contain the |
NO |
Android |
Android supports the use pre-roll, mid-roll, and post-roll events. |
NO |