Some use the word "Streaming" to describe any video that's playing in their browser.
But just because you are watching a video online, doesn't mean it is being "Streamed". Maybe true in the general meaning of the word, but not true in the technical sense. Let me explain, because it might not be of relevance to regular folks, but it is highly relevant to digital content creators.
Regular videos - aka “progressive download” videos - are progressively (aka continuously) downloaded to the viewer’s browser first, even if the video has been paused. And that's why using plugins like Video Downloader and Video Downloader will let you download the video you’re watching.
But as a creator, progressive download videos can increase your bandwidth costs to deliver that video. That's because, as soon as the viewer hits "Play" on the video, the video starts to download to their computer (in whatever the "temp" folder of the browser is, where it stores all temporary internet files).
And then, even if the viewer clicked "Pause" right after they clicked "Play", the video will still continue to download all the way until it is completely downloaded. So if it's a big file, then the entire file of tens- or hundreds of MB's of data is downloaded to their device first (whether it's their computer or mobile device). And regardless of whether they end up watching a few seconds video or a few minutes of the video, the video was downloaded in full to their device.
That means, the video provider (your S3 account) ended up delivering the entire video, even though they may or may not watch it, or only watch it partially.
So more bandwidth cost for you, the creator. And for the viewer as well, their internet bandwidth is used to download the full video, even though they may or may not watch it, or just watch it partially. So more bandwidth costs for your viewer as well. And especially more so if they're on a mobile device and are using their data and have a limited data plan.
And that's where "Streaming Video" is much more beneficial to everyone involved - well, almost to everyone involved, which I'll explain in a minute. And that's because with streaming video, the video is delivered as a "download as you watch" stream of data. The web service Amazon MediaConvert converts the single .mp4 file into a number of smaller chunks of file "segments" which have the extension ".ts".
There could be tens or hundreds or thousands of such segments depending on how long the video is. And those segments are delivered one by one to the viewer's device, as they continue to watch the video. But if the viewer hits Pause on the video player, then the segments will stop being downloaded.
So only the bare-minimum amount of video data is delivered to the viewer, as need, as they continue to watch. And that ends up saving you - the provider - money in terms of bandwidth costs; and also reduces the viewer's data usage as the consumer.
But there are two small downsides to streaming:
1) It costs a bit more in terms of your AWS bill, because to create a streaming video, you need to use Amazon MediaConvert, a cloud-based service that can take a .mp4 file and convert it into streaming "segments" (but it's a one-time cost).
2) If some of your audience are from countries where they have slow or poor internet access, streaming videos will be almost unwatchable to them, because their internet access will never be fast enough to download the video "segments" fast enough for them to continue watching normally. And may result in the video freezing up every few seconds while the downloading of the segments catches up to their viewing. But with progressive downloads, those who have poor internet access speeds, will be able to hit Play on the video, then hit Pause, and come back in however long, and the video would continue to download the whole time they're away from their device, because that's what progressively downloading means. But you can't do that with streaming where you can Play, Pause and come back later to a fully downloaded video, because the video doesn't download full with streaming.
So if you deliver your videos as regular "progressive downloads", you need just Amazon S3, and you get possibly (slightly) higher bandwidth costs because the video is fully downloaded to the viewer's device regardless of how much of it they watch.
And if you deliver them as "streaming videos", then you'll need S3 + CloudFront + MediaConvert. So the addition of CloudFront and MediaConvert increases your costs slightly, but you could also end up saving a little bit on the bandwidth costs, because only as much of the video is necessary, is delivered to the viewer's device.
Using S3MediaVault, you can create both progressive download videos as well as true-streaming videos that cannot be downloaded.
They’re both secure, but Streaming Videos are the most secure because they are streamed in real-time, in segments, to the viewer’s browser. And that means plugins like Video Downloader, Video DownloadHelper and even the most popular video downloading software Internet Download Manager won’t be able download your video (their only option is to record their screen to make a copy).
S3MediaVault uses Amazon AWS MediaConvert service to create the streaming version of your mp4 and then delivers that to your viewer, and makes it really easy and manage everything from within WordPress without having to log in to AWS or know any of the technical stuff behind creating a streaming video.
Amazon S3 Pricing: How Expensive is it to use S3?
What are the benefits of using Amazon S3?
How (and Why) to use Amazon S3 to Deliver Audio, Video and PDF on your WordPress website
Storing Video & Audio On Your Website (Hint: Don’t!)
How can I stream videos in my Amazon S3 account in my website?
Amazon S3 Audio Player
Voice & Recording Tips for Podcasters & Video/Audio Creators