Simplicity
Easy to use video hosting platform
Upload a file, let it transcode, copy the embed snippet into your page. That is the whole path from a recording on your desktop to adaptive video playing on your own site, and it does not require anyone on your team to know what a bitrate ladder is. Everything harder than that — renditions, packaging, delivery, encryption — happens for you.
The workflow
What publishing one video actually involves
Four steps, in order, with nothing hidden between them.
- 01
1. Upload the file
- 02
2. Transcoding runs for you
- 03
3. Copy the embed snippet
- 04
4. Read the engagement report
Why it stays simple
A simpler workflow from upload to published playback
Video is genuinely complicated. Most of that complexity is handled once, centrally, and never surfaces in your workflow.
- Renditions and packagingAutomatic
- One source file becomes an adaptive set. A viewer on a poor mobile connection and a viewer on office fibre both get a stream that suits them, without you preparing two versions.
- Projects carry the settingsReusable
- Group videos into a project and the shared configuration travels with them, so the twentieth video does not need the same setup decisions as the first.
- Protection is a setting, not a buildEvery plan
- Encrypted delivery is on by default on the plans, and restricting playback to your own domains is a list you populate rather than code you write. Signed private links are generated per video when you need one.
- Captions where you expect themCaptions
- Upload an SRT or VTT file per language against a video and it becomes a selectable subtitle track. Text can be corrected in place later without re-uploading.
- The API mirrors the dashboardEvery plan
- Anything you do by hand can be scripted: upload sessions, video and project management, captions, embed retrieval and webhooks that tell your system when a video is ready. Included on every published plan.
- One place for thumbnails and chaptersPer video
- Thumbnails and chapter markers are managed alongside the video itself, so preparing a long recording for publication is a single sitting rather than a checklist across tools.
Who it suits
Who finds this genuinely straightforward
Educators and trainers
Record a lesson, upload it, drop the snippet into the course page. Captions and chapters make a long recording navigable without editing software.
Marketing teams
Publish a product video on a landing page with your own brand around it, then read completion rates to see whether the message lands.
Support teams
Short how-to clips embedded beside the article they explain, added by whoever writes the article rather than a specialist.
Developers
Skip the dashboard entirely. Drive upload sessions, publishing, captions and reporting from your own code, on any plan.
Solo creators
One person can run the whole workflow without a producer, an encoder or a CDN configuration to maintain.
Small teams sharing the work
Seats are not a billing dimension, so whoever has the video can upload it without asking someone else to do it for them.
Questions
What people ask before their first upload
How do I get a video onto my website?
Upload the file, wait for transcoding to finish, then copy the embed snippet for that video into your page. The player renders inside your own layout with your configured appearance, and delivery adapts to each viewer’s connection automatically.
Do I need to prepare or convert my video first?
No. Upload the best source file you have and transcoding produces the adaptive renditions for you. You do not choose codecs, resolutions or segment settings — that is the part a hosting platform exists to absorb.
How long does processing take?
It depends on the length and resolution of the file, and a long high-resolution video takes noticeably longer than a short one. Give the first upload of a launch a day of headroom, and use a webhook if you want your own system to be told the moment a video becomes playable rather than polling for it.
Can I upload a lot of videos at once?
Yes. For anything more than a handful, use resumable upload sessions through the REST API rather than the browser, and let webhooks report completion. Smaller plans carry fewer concurrent conversion slots, so a large batch processes steadily — worth knowing on migration day.
Does my team need technical skills?
No. Uploading, embedding, adding captions and reading the reporting are all dashboard tasks. The API exists for teams who would rather automate, not as a requirement for teams who would not.
Will the player match my site?
The player is configured per project and renders inside your own page, so it sits in your layout rather than imposing a destination’s design, and there are no adjacent recommendations pulling viewers away. Configure it once and the setting travels with every video in the project.
What if I need to replace a video later?
Manage the video through the dashboard or the API, and keep the embed in place on your page. Captions can be edited in place, thumbnails and chapters updated, and video state read back through the API so your own systems stay in step.
Try the sequence on one real video
Upload something you actually need published, wait for it to process, and paste the snippet into the page where it belongs. Four steps is the honest answer, and one video proves it.