Video on the web feels like it is in an awkward middle stage at the moment.
For years, Flash has been the dependable answer for putting video into a website. It is not perfect, but it is familiar and widely understood. Now HTML5 video is becoming more serious, and the idea of placing video directly into the page without a plugin is appealing. The problem is that the practical decisions are not as clean as the idea.
The question on a client project is not which technology sounds more modern. The question is whether the visitor can actually watch the video, whether the site remains usable and whether the business is relying on something that will fail for part of its audience.
Why HTML5 Video Is Appealing
The appeal of HTML5 video is clear. The markup is simple, the video becomes part of the page and the browser can handle playback without requiring a separate plugin. That feels like the direction the web should move in. It also makes the page structure easier to understand because the media is not hidden behind an embedded player in the same way.
<video controls>
<source src="/media/example.mp4" type="video/mp4">
<p>Your browser does not support this video.</p>
</video>That simplicity is attractive, but it does not remove the support problem. Different browsers have different expectations around formats, and that means the implementation still needs thought.
Flash Is Still There For A Reason
It is easy to talk about Flash as if it is already finished, but that does not reflect how many websites and users still depend on it. For many visitors, Flash video simply works because the plugin is already installed and the player behaviour is familiar. On a client site, that reliability matters.
The issue is that Flash also creates dependency. If the plugin is missing, disabled or poorly supported on a device, the video becomes unavailable. It can also feel heavy, especially on machines that are less capable. For content that is important to the business, relying on one plugin-based route is not ideal.
This is the awkward part. HTML5 video feels cleaner, but Flash may still reach users that HTML5 does not. Flash feels established, but it does not fit comfortably with the direction browsers and devices appear to be moving.
The Content Should Decide The Effort
Not every video deserves the same amount of technical effort. A decorative background clip, a small promotional piece and an essential training video are different problems. If the video is central to the page, the fallback and format decisions matter more. If it is supplementary, I may choose a simpler approach and avoid making the page heavier than it needs to be.
I also want to avoid autoplaying video unless there is a very good reason. Automatically loading and playing media can make a page feel slower and more intrusive. The visitor should usually choose to play the video, especially if they are on a slower connection or using a device with limited battery.
The better question is not how to show off the video. It is how to make the video available without damaging the rest of the experience.
How I Would Handle It Now
For the moment, I would handle video with a layered approach. Use HTML5 video where support allows it, provide sensible source formats and consider a fallback where the audience requires it. The exact answer depends on the project, the content and the visitors.
I would also make sure the page around the video still works. A visitor who cannot play the video should not be left with an empty hole and no context. A transcript, summary or alternative route can be useful, especially when the video contains important information.
This is one of those areas where the web is clearly moving, but the present is messy. The best decision is probably not to be purist. It is to make sure the content remains accessible while the technology settles.