Peachify Embed: a movie on your site in one minute

What the embed actually is

An embed is a deal: your page lends a rectangle, and Peachify fills it with a player. The rectangle is an iframe; the player is a web app that knows how to turn a TMDB ID into a stream. Nothing on your server changes — no new files, no new packages, no database table for video.

The link carries everything the player needs. For a film, the number is the whole request:

https://peachify.net/movie/533535

That is not a shortened link or a redirect. It is the address of the player, already pointed at the film. Change the number, change the film.

The one-minute version

Three moves, and you are done.

1. Find the number. Open the title on themoviedb.org. The URL looks like themoviedb.org/movie/533535 — the number at the end is the ID.
2. Make the link. Put the number after peachify.net/movie/. That is the embed URL.
3. Paste the frame. Drop this into your page, inside a box that is 16:9:

<iframe src="https://peachify.net/movie/533535"
  style="width:100%;height:480px"
  frameborder="0" allowfullscreen></iframe>

Save, reload, press play. If it plays in the live demo, it plays on your page — the demo is the same player, just sandboxed.

TV is the same trick, twice

TV adds two numbers and nothing else: a season and an episode. The pattern is:

https://peachify.net/tv/1399/1/1

Season 1, episode 1 of that show. Want episode 2? Change the last number. Want season 3? Change the middle one. A whole series page is a list of links that differ in two digits — no re-encoding, no re-uploading, no new embed code per episode.

Where the embed fits

Anything that accepts an iframe. WordPress takes it in a Custom HTML block. React, Vue, and Next.js render it like any other element. A plain HTML page takes it raw. Static hosts, site builders, and headless CMSs all work, because the embed is a standard iframe — there is no framework-specific code to install and no plugin to keep updated.

It also fits the places people actually watch: phones, tablets, laptops, and desktops. The player is responsive and touch-first, so the frame scales to the width you give it and the controls stay thumb-sized.

Four mistakes that break an embed

Most broken embeds fail in one of four ways, and all four are quick to fix.

1. The wrong number. The TMDB ID is the number in the title's themoviedb.org URL — not the year, not the IMDb ID, not the title typed as text. If the player loads to nothing, re-check the digits first.
2. A frame with no height. An iframe with no height renders as a sliver. Give it a fixed height (480px works on desktop) or a 16:9 aspect-ratio box, and the player has room to breathe.
3. Mixing http and https. A page served over https that embeds an http player will be blocked by the browser. Use the https Peachify link and the problem disappears.
4. Sandboxing your own embed. The strict sandbox belongs on the homepage demo, where ads must never fire. On your own site, use the clean link with no sandbox — a sandboxed frame can block the very popups the ad-supported player needs.

Fix the number, the height, the scheme, and the sandbox, and the embed plays. If it still does not, open the same link in the live demo — if it plays there, the link is fine and the page around it is the problem.

Why it stays free — and why that is honest

Peachify costs nothing because the player is ad-supported. Ads run on the embed, and they pay for the service. There is no paid plan, no locked feature, and no surprise invoice. The homepage demo shows no ads because it is a sandboxed preview; your own site's embeds run the ad-supported player, as the player guide explains.

Peachify does not host, store, or manage any media files. The player aggregates publicly available sources and routes them by TMDB ID. If you want the developer version of this page — endpoints, snippets, and automation — the Peachify API guide has it.