Video to URL: Upload Limits, Resume a Large File and Embed the Result

A video link is ready to share only after the service returns the published result. Selecting a file creates a local preview; transferring all of its bytes is another step; validation and publication can still be pending. This guide follows the actual video upload tool, reviewed on October 22, 2026.

Choose the route that matches your account and file

The limits below use binary units: 1MiB is 1,048,576 bytes and 1GiB is 1,073,741,824 bytes. Some interface labels abbreviate them as MB or GB. Check the file's actual byte size when it is close to a boundary.

Large-file availability is determined by the current service configuration and account entitlement. Plans and pricing explain the account options; terms govern use. Quotas, validation and capacity checks still apply to paid uploads.

Prepare a file that can be checked and played

The tool accepts MP4, MOV, AVI, WebM, MKV, MPEG/MPG, OGG/OGV, 3GP and FLV extensions. A supported extension is not proof that the file contains valid video or that every browser can decode its tracks. Renaming an unrelated file to .mp4 does not convert it.

For example, export product-demo-2026-10.mp4, open it locally and confirm that the picture, sound and ending are intact. This is an illustrative filename, not a supplied demo asset. If the audience uses ordinary web browsers, a commonly supported MP4 encoding is a practical starting point; test the actual browser and device you intend to support. The host does not turn every source format into adaptive streaming versions or generate a transcript for you.

Complete a conventional upload

1. Open Video to URL and select or drop one video.
2. Check the displayed filename, size and preview. The preview uses a local browser object URL and is not your public link.
3. Start the upload. Keep the page available while the request completes.
4. Copy the returned direct URL only after the result panel reports success.
5. Open that URL separately and confirm that the intended file is reachable. Check playback in the destination browser before publishing an embed.

A direct URL can be opened or downloaded by someone who receives it. Do not treat an obscure filename, HTTPS or an unlisted link as recipient authentication. Use a different access-controlled system for confidential recordings.

Resume a file above 500MiB

For an eligible large video, the browser first computes a content fingerprint. That preparation reads the file and can take time before network transfer begins. The service uses 32MiB parts and at most three parallel part uploads. A complete 1GiB file therefore has 32 parts.

Use Pause while transfer is active if you intend to continue. Resume with the same original file and account; do not edit, rename or re-export the file between attempts. The server checks its recorded identity and returns the parts already present, so the client sends the missing parts. If the page was closed, reselect the original file and start the flow again while the session remains valid. The browser does not save the actual file for you.

Cancel is different from Pause: it requests abandonment of that upload. It is not a way to preserve a session for later. Once the tool is validating, keep the status visible rather than starting another copy. Completed parts do not mean the file is published; wait for the ready result after full-file checks and publication.

What has already been verified

The documented October 19 acceptance included a synthetic 1GiB file, interrupted transfer recovery, full-file scanning, publication and a complete download whose SHA-256 matched the source. That upload ran on 3882a1b; final acceptance of f62aa54 retained the same upload core. Temporary test objects were removed. This is a historical acceptance record, not a new experiment for this article, a live sample link, or a promised completion time. See the release notes for the published feature history.

Embed the confirmed result

The result panel offers a plain URL, Markdown, HTML video markup and a BBCode link. For an ordinary document, the plain link is often sufficient. For a web page, use a player only if that page supports HTML video.

<video controls src="YOUR_CONFIRMED_VIDEO_URL" preload="metadata">
  Your browser does not support this video. Use the direct download link.
</video>

Replace the placeholder with the URL returned by your upload. This is an example, not a working hosted video. The player still depends on the browser's codec support and your site's configuration; MDN's video element reference explains the relevant attributes.

Diagnose the stage that actually failed

For a published video page rather than file delivery alone, continue with the watch-page and indexing guide.