Embed a movie with this Videasy player
<iframe src="https://www.videasy.xyz.peachify.net/embed/movie/533535" allowfullscreen></iframe>
Replace 533535 with any TMDB movie ID.
Embed a TV episode
<iframe src="https://www.videasy.xyz.peachify.net/embed/tv/1396/1/1" allowfullscreen></iframe>
That example is TV ID 1396, season 1, episode 1. Change the three numbers for any other episode.
What the player does
- Adaptive playback: quality adapts to the viewer's connection, instead of locking to one file.
- Subtitles: subtitle support is built in, with English on by default in the current build.
- TV navigation: season and episode are in the URL, so deep-linking to an exact episode works.
- No key in the iframe: nothing secret is exposed in the embed code you paste into a page.
- Works in any site builder: a plain iframe works in HTML, WordPress custom HTML, React, Vue and static sites.
Switching from a Videasy player embed
If your pages already use Videasy player iframes, keep every TMDB ID and every season/episode number. Only the base URL changes, from the Videasy base to the Videasy embed base shown above. That is the whole migration for most sites — no database change, no new ID mapping, and no extra page per title.
For the API-level details, see the Videasy API. For the full overview, see the Videasy hub.
Videasy Player in depth
A player built around one idea: the URL is the setup
Most players need configuration before they play anything: a source file, a playlist, a key, or a per-title setup step. The Videasy player works the other way round. The URL already contains everything it needs — the title type, the TMDB ID, and, for TV, the season and episode. Open that URL in an iframe and playback starts from there. That is why a Videasy player embed can be copied from page to page with only the numbers changed.
This page explains what the player does once it loads, how to size it correctly, how it behaves on different devices, and what to check when playback does not start. It does not promise features the current build does not have: the player UI, quality handling and subtitle behaviour described here are the ones in the embed examples on this site.
What the Videasy player does when it loads
Adaptive playback
Quality follows the viewer's connection instead of locking to one fixed file. On a fast connection the player can use a higher quality; on a slow connection it drops down rather than stalling on a file the connection cannot sustain.
Subtitles built in
Subtitle support is built into the player, with English subtitles on by default in the current build. Viewers do not need a separate subtitle file or a separate integration step on your page.
Fullscreen and responsive sizing
The player is an iframe, so fullscreen comes from the standard allowfullscreen attribute, and responsive sizing comes from the wrapper around it. Set the wrapper to 100% width and a 16:9 aspect ratio and the player fills it on phones and desktops alike.
Exact-episode deep links
For TV, the season and episode are in the URL. A shared link therefore opens that exact episode, which matters for episode guides, recaps and social posts that point at one episode rather than a whole series.
Setting up the Videasy player in three steps
Choose movie or TV. Movies use /movie/{TMDB_ID}. TV uses /tv/{TMDB_ID}/{SEASON}/{EPISODE}. Do not swap them: a movie ID in a TV URL, or a TV ID in a movie URL, will not load the title you expect.
Wrap the iframe in a 16:9 container. The container should be 100% wide, with an aspect ratio of 16:9, and the iframe should fill it. That single wrapper is what makes the same embed work on a phone screen and a desktop monitor.
Test one movie and one episode. Test on a phone and a desktop, with subtitles on, and in fullscreen. If both test pages work, the template is safe to use across the rest of the site.
position: relative; padding-top: 56.25%; and give the iframe position: absolute; top: 0; left: 0; width: 100%; height: 100%;. That is the standard 16:9 responsive iframe pattern, and it works with the Videasy player without any player-specific code.Videasy player on different devices
On desktop, the player behaves like any other browser video player: fullscreen, subtitles and adaptive quality all come from the player itself. On mobile, the same iframe works in the mobile browser, but the wrapper matters more, because a fixed-width iframe will overflow a small screen while a 100%-width wrapper will not. There is no separate mobile player to configure, and no app to install, for either the site owner or the viewer.
For TV browsers and large screens, the same rule applies at the other end of the scale: a 100%-width wrapper lets the player use the available width, while a small fixed width leaves the player tiny on a large display. Size the wrapper, not the player, and the player will follow it.
Troubleshooting the Videasy player
- Blank player: check the TMDB ID, the title type, and the season/episode numbers. Then check that the embed base URL in the iframe matches the one on this page.
- Wrong title: you are almost certainly using the wrong ID, or a movie ID where a TV ID was needed. Re-check the title on themoviedb.org.
- Player overflows on mobile: the wrapper is fixed-width. Change it to 100% width with a 16:9 aspect ratio.
- Subtitles not showing: check the subtitle control in the player itself. The current build has English subtitles on by default, but the viewer can change subtitle settings in the player.
- One page works, another does not: compare the two iframe URLs character by character. A single wrong digit in an ID is enough to break one embed while the rest of the site works.
For the endpoint pattern behind the player, see the Videasy API. For streaming pages, see Videasy streaming.