DynTube Developer Resources

Use these guides to add DynTube playback to web and mobile applications, select videos dynamically, or move an existing library into DynTube. Each workflow starts with the current generated embed or playback data and keeps account credentials in trusted server code.

Web player integrations

• Next.js — render a responsive iframe in a Server Component and add the v2 SDK in a Client Component when player control is required.
• React — build a reusable iframe component with a stable player ID, then manage SDK setup and cleanup through the component lifecycle.
• Dynamic videos and channels — select trusted generated embeds from application data without storing arbitrary HTML.

Mobile HLS playback

• AndroidX Media3 ExoPlayer — play a DynTube HLS URL in a native Android screen and release the player with the screen lifecycle.
• React Native — pass authorized HLS playback data to a maintained native video component and test protection on real target devices.

Library migration

The Vimeo migration guide shows a server-side transfer: obtain an authorized downloadable source from Vimeo, submit that source URL to DynTube, record the returned video ID, and follow processing to publication. This avoids downloading every source through a browser.

Current embed contract

<iframe
  id="dyntube-YOUR_EMBED_KEY"
  src="https://dyn.tube/embed/video/YOUR_EMBED_KEY?playerId=dyntube-YOUR_EMBED_KEY"
  title="Describe this video"
  allow="autoplay; fullscreen; encrypted-media; picture-in-picture"
  allowfullscreen
  style="width:100%;aspect-ratio:16/9;border:0"></iframe>

Copy the generated embed from the DynTube dashboard whenever possible because an account may use a different playback host. Add the v2 module SDK only for events or methods; ordinary iframe playback needs no bootstrap script.

Security checklist

• Keep DynTube API keys, signing keys, and provider credentials on your backend.
• Authorize the viewer before returning protected playback data.
• Use short-lived links and allowed origins where the project security policy requires them.
• Treat embed keys as media identifiers, not API credentials.
• Test the exact browser, mobile device, captions, network conditions, and protection mode your application supports.