So you’ve uploaded your video to FastPix. Now what?
This guide walks you through everything you need to start playing your videos - whether you’re building a web app, integrating into a mobile SDK, or need a direct HLS URL.
Every video uploaded to FastPix is assigned a unique mediaId. To play the video, you’ll need its corresponding playbackId.
You can get the playbackId using the Get Media by ID endpoint:
FastPix supports HLS playback out of the box. Once you have the playbackId, you can build the video stream URL like this:
So if your playbackId is 837f028b-dcaf-4c23-b368-3748641f74ac, your HLS URL becomes:
This URL can be plugged into any HLS-compatible player (web, mobile, or smart TV).
To directly stream your video on a browser, you can also use the playback stream URL which is sharable. Simply preview your video by putting the playbackId on the stream URL.
Parameters
Specifies the exact output resolution (width × height) for a single rendition.
Use this parameter when you want the system to generate media stream at a specific, fixed clarity.
The highest resolution allowed or generated for a media file.
Used to set the highest desired resolution.
Example: If max_resolution = 1080p, the output renditions will not exceed 1920×1080, even if the source is 4K.
The lowest resolution allowed or generated for a media file.
Used to ensure the lowest-quality fallback for poor bandwidth.
Example: If min_resolution = 360p, the system always generate at least 640×360 or similar.
rendition_order:
Defines the sequence in which multiple renditions appear.
When set to asc, renditions are listed from the lowest resolution to the highest resolution.
When set to desc, renditions are listed from the highest resolution to the lowest resolution.
When min_resolution and max_resolution are both specified, you can still use rendition_order to control whether the resulting renditions appear in ascending or descending order.
NOTE
You cannot use
resolutiontogether withmin_resolutionormax_resolutionin the same request.
You can integrate uploaded videos in FastPix Player which is built-in with video data tracking to enhance your application’s media experience.
See how to use iframe to embed video.
FastPix supports adaptive HLS playback via .m3u8 URLs. These can be used in any video player that supports HLS including open source and commercial options.
Your HLS stream URL:
Below are integrations with popular players used in production.
When to use: You want full control over playback, and you’re okay building your own UI.
When to use: You need DASH + HLS support, buffer management, or recovery logic.
When to use: You want a battle-tested open-source player with a customizable UI.
You can also integrate hls.js for better cross-browser behavior if needed.
For a better developer experience, we recommend using the FastPix Player SDK, which automatically handles:
NOTE
FastPix Video Data is built-in and automatically tracks video performance and engagement.
Here’s how to use it on the web:
Refer to the player guide for more details on integrating with the FastPix video player. You can further customize your player interface and video playback experience as per your requirements.
After you have successfully implemented the integration, connect FastPix Video Data with your player to monitor playback performance. Once videos start playing, FastPix Video Data automatically collects:
Go to your FastPix Dashboard > Video Data > Metrics or use the Video Data APIs to pull real-time insights.
If your video requires access control (For example: for paid content, internal tools, etc.), you can enable Signed URLs to add expiry and signature to your playback URLs.
Refer to the Protect Videos guide for setup instructions.
Not every highlight needs a new clip. Sometimes, you just want to show a segment of a video - without downloading, editing, or creating a new file.
FastPix now supports instant VOD clipping (segment playback) using just a URL. This lets you stream a portion of any video by simply appending start and end timestamps to the playback URL. The original asset remains unchanged - there’s no encoding, splicing, or new file creation involved.
It’s perfect for previews, highlights, and in-app playback customizations.
Every FastPix video comes with a playback URL that looks like this:
https://stream.fastpix.com/{PLAYBACK_ID}.m3u8
You can extend this URL with query parameters to define where playback must start and/or stop - without modifying the underlying video file.
These parameters are optional and can be used independently or together.
Rules
start and end are optional.start is provided → playback begins from that timestamp until the end of the video.end is provided → playback begins at 0 and stops at that timestamp.Let’s say your playback ID is abc123. Here are some real URLs:
1. Play from 20s until end:
https://stream.fastpix.com/abc123.m3u8?start=20
2. Play from beginning until 455s:
https://stream.fastpix.com/abc123.m3u8?end=455
3. Play only between 20s and 455s:
https://stream.fastpix.com/abc123.m3u8?start=20&end=455
This is useful when you want to play a portion of a video, not republish it:
Playback control happens at the HLS segment level. So the start and end times might not be exactly frame-accurate. This means playback may be off by a few seconds (typically 2–3s).
For example, this means a start=20&end=60 might actually start at ~18s and end at ~63s.
If you need precise trimming, use the Clipping API to generate actual clips from source files.
When to use this vs the Clipping API