Why xHamster’s MP4 Files Stop at 720p
Every downloader that promises an instant 1080p from a logged-out page is either mislabelling a 720p file or upscaling one. Here is what xHamster actually publishes as a file, where the higher renditions really live, and how to check both.
The ladder is four rungs long
The data an xHamster player is built from sits in the page’s own HTML. On some videos it carries an open list of downloadable files, and that list holds exactly four rungs: 144p, 240p, 480p and 720p. Each one arrives with a byte count attached, which is where the sizes on this site come from — they are not estimates.
On most videos that list is no longer published openly. The same four files are still there, with their addresses scrambled inside the player payload instead. Either way the ladder is the same length: it does not grow for longer videos, popular videos, or videos from verified uploaders. Four rungs is the whole ladder.
A 4K source does not change it
The obvious objection is that the ceiling must depend on what was uploaded. It does not. We checked a video whose stored resolution is 3840 × 2160 — genuine 4K — and the download list still stopped at 720p.
Worth knowing if you go looking yourself: the flags xHamster sets on a video are not reliable. That 4K video reported false for its own ultra-HD flag. The resolution field is the honest one.
Where 1080p and above actually live
The higher renditions do exist. They are delivered through an adaptive stream — the format that lets a player step up and down in quality as your connection moves — and an adaptive stream is not one file. It is a playlist pointing at hundreds of short fragments, four seconds each, with no way to ask for the whole thing at once.
So handing you a 1080p MP4 means fetching every fragment, joining them in order, and re-wrapping the result. Done on a server that is expensive — a 248 MB download costs the server 248 MB in and 248 MB out — which is why most tools quietly do not offer it, and why the ones that claim to are usually relabelling a 720p file.
It can also be done on the machine that actually wants the file. This site lists those renditions as rows tagged “stream”: your browser fetches the fragments straight from xHamster, joins them locally, and saves the result, so the video still never touches our server. The trade is worth stating plainly — it takes a minute or two instead of being instant, the size shown is an estimate from the stream’s bitrate rather than a measurement, and a 4K build needs roughly twice its finished size in free memory, which makes it a desktop job.
Two ways to check any claim
The direct way: open a video page and view source. If that video still publishes its list openly you will find the four MP4 entries with their byte counts; if it does not, you will find the scrambled player payload instead, and the same four qualities are inside it. What you will not find, on either kind of page, is a ready-made 1080p or 2160p MP4.
The lazier way: download the 720p from any tool claiming an instant 1080p and look at the file’s properties. If the frame height reads 720, you have your answer. If it reads 1080 but the picture looks soft and the file is barely larger, it was upscaled — which throws away nothing and adds nothing except megabytes. A genuine 1080p is several times the size of the 720p and takes time to appear, because it had to be assembled rather than downloaded whole.
Which rung to actually take
For phone viewing, 720p is already more than the screen resolves at normal viewing distance, and it downloads instantly. For a laptop it is fine. On a large television it will look soft.
That is the case where building the stream earns its minute or two — but only when the video has a higher rendition at all, and only on a desktop with the memory to spare. Everywhere else the practical move is to take the 720p and know exactly what you have, rather than paying for a tool that delivers its promised number by relabelling.