The short answer
The list shows the versions Dailymotion currently has for that video. If 1080p is not in it, no tool can produce a real 1080p file — enlarging a smaller one adds pixels, not detail. On 2026-10-29 the three public videos we checked topped out at 848×480 (landscape) and 480×848 (portrait). The 1080p option was simply not there.
The labels are rung names, not pixel sizes
This is the part the old version of this page got wrong. Each entry is named after a step in Dailymotion's encoding ladder — hls-1080, hls-720, hls-480, hls-380 — and the number is not a promise about the file. Here is what six versions turned out to be:
| Video | Label in the list | Actual size | How we know |
|---|---|---|---|
| Storm clip, 38 s | hls-480 | 848×480 | downloaded, ffprobe |
| Storm clip, 38 s | hls-380 | 512×288 | downloaded, ffprobe |
| 49ers clip, 507 s | hls-480 | 848×480 | resolver metadata |
| 49ers clip, 507 s | hls-380 | 512×288 | resolver metadata |
| Drama episode, 21 min, portrait | hls-480 | 480×848 | resolver metadata |
| Drama episode, 21 min, portrait | hls-380 | 360×640 | resolver metadata |
Two things follow. A "380" entry can be 288 pixels tall, and on a portrait video the "480" entry is 480 wide and 848 tall — the number counts the short edge, not the height. Read the pixel size next to each entry, not the rung name.
The same clip had more versions two days ago
We resolved this exact 38-second storm clip on 2026-10-24 and it listed four rungs — hls-1080, hls-720, hls-480, hls-380 — and the 1080p file we downloaded then was 1920×1080, 21,398,476 bytes. On 2026-10-29 the same clip lists only hls-480 and hls-380, and the 480p file is 848×480, 3,769,292 bytes.
We do not know why the higher rungs disappeared — that is Dailymotion's side of the chain, and this observation does not tell us whether they were removed, made conditional, or simply not offered to this request. What it does mean for you: a 1080p version existing yesterday is not evidence that it exists today. Re-resolve the link instead of trusting an old result.
What the list does and does not tell you
- No file size before you choose. Dailymotion reports no size for these versions, so the list shows none — it cannot tell you that 480p will be 3.7 MB and 288p 2.1 MB until you pick one.
- Accurate size after you choose. Once a version is prepared, the size shown matched the delivered file exactly in our two tests (3,769,292 and 2,115,462 bytes).
- Sound is in every version. Both downloads carried an AAC track. The lower rung is not just smaller, it is thinner: 128 kbps stereo at 480, 64 kbps stereo at 288.
- No automatic "best" pick. There is no recommended row and no hidden default — the list is what exists, in ladder order.
Step by step
www.dailymotion.com/video/x… or dai.ly/x…. The mobile m. host, /embed/ links and bare IDs are rejected — use the full www address.Known limits
- 30 minutes / 500 MB per file. Two different checks: the duration is tested while the link is read (a 28:55 video passed, a 41:33 one was refused in about 4 seconds without transferring anything); the size is tested after the file is written, so an oversized file fails at the end instead of the start.
- 10 link reads and 6 download starts per 10 minutes from one address. Over that you get HTTP 429 with a wait time.
- One file is built at a time, with a short queue.
- Some videos fail outright, and the reason is one level down. Two of the five IDs we took from this site's own access log came back with no version list at all. We first read that as "no error code"; on 2026-10-31 the same two IDs both returned
NOT_FOUND_OR_PRIVATE. The reason is not missing, it is nested: the top level says only failed, and the code sits inresult.codebeside an empty task list. That code covers three cases it cannot separate — removed, made private, or no longer resolvable — so treat it as "not available now", not as a bug a retry will fix. If you see a bare failure with no reason at all, the response is incomplete rather than a different fault.
The rest, including what each error code means, is on What VidMotion cannot do and Dailymotion download not working.
How this was measured
2026-10-29, from our own server against three public videos found in this site's own access log. Pixel sizes of the two downloaded files were read with ffprobe after download; the other four come from the resolver response. Not tested: a phone, Safari, and the browser's own download dialog — this covered the file layer only.
FAQ
Why is 1080p missing for this video?
The version is not being offered by Dailymotion right now. Our own test shows this can change from one day to the next: the same clip listed a 1920×1080 rung on 24 October and did not on 29 October. No downloader can create a higher-resolution source that does not exist.
Is the largest file always the best choice?
Not necessarily, and on this site you cannot even compare sizes before choosing — the list has none. Pick the pixel size you actually need; a 848×480 file is enough for a phone screen and a fraction of the bytes.
Does it upscale?
No. Every version is fetched as Dailymotion encoded it. Nothing is enlarged, and nothing is re-encoded on our side.
How to verify a 1080p result
Check the dimensions of the downloaded video track in the file properties or player media information. A horizontal 1920 by 1080 frame is Full HD; a vertical recording may be 1080 by 1920. The filename or the size in megabytes does not establish the resolution.
Compare the same moment in the source and saved file at the same display size. A higher pixel count cannot restore detail missing in the original. If 1080p is unavailable for that video, use an available rendition or obtain the original export from its owner.