Are files uploaded for this tool?

This browser tool processes the selected media locally on this device. The file is not uploaded to ArtPlayer servers for this workflow.

Will the export have a watermark?

No. ArtPlayer browser tools do not add watermarks to exported files.

Why can processing take time?

The work runs in your browser, so speed depends on your device, browser, memory, source size, and the export settings needed for the result.

Which browsers work best?

Recent Chrome, Edge, and other modern Chromium browsers usually work best for heavier browser media processing.

What should I try if a large file fails?

Try a smaller source, close other heavy tabs, reduce resolution or duration first, and keep the tab open until the export finishes.

Why does HLS create multiple files?

HLS output includes playlists and media segments so players can stream the video in chunks.

Where are the HLS files written?

The browser workflow writes the generated package to a directory you choose when supported.

Can I create an HLS package from a video?

Yes. The tool writes playlist and segment files for a browser-generated HLS VOD package.

Why is the result a folder instead of one file?

HLS uses a playlist plus media segments, so the output is a set of files rather than a single MP4.

Which output quality does the HLS package include?

Choose an output preset before creating the package. Each preset writes a different set of video renditions, and the preview lets you switch between them.

Which browsers can preview the local HLS package?

The preview needs a browser with Media Source Extensions and File System Access support. The package itself is written locally by the browser.

Browser streaming tool

Video to HLS

Browser-nativeHLS outputMulti-file export

Generate a multi-rendition HLS package in the browser and write the manifest plus segments into a local directory.

Source video

Drop a file here, or click to choose

Output directory

Output preset

Video renditions

H.264 AVC

Audio rendition

AAC

How it works

Three steps to finish the browser workflow.

1
Source video
Drop a source video here, or click to choose one.
2
Output directory
Choose a writable directory for the manifest and segments.
3
Create HLS package
This page uses Mediabunny plus browser encoding support to create several AVC renditions, package them as HLS, and write every output file into a directory you pick.

Everything you need

Core details about privacy, browser support, output, and practical limits before you start.

Local packaging

The source video stays in this browser session and is encoded without sending bytes to a server.

Multiple renditions

Creates a ladder of 1080p to 240p AVC variants plus a shared AAC audio track for a normal VOD package.

Real file tree

Writes a manifest plus segment files into a user-selected directory.

Input, output and limits

Check supported inputs, output formats and usage requirements before you start.

Supported input	Video files such as MP4, MOV and WebM. Container and codec support depends on the browser and processing runtime.
Output result	An HLS folder containing playlists and media segments, saved to a directory you choose.
Processing and privacy	Processing runs on this device. Source media is not uploaded for this workflow.
Browser requirements	Saving to a folder requires File System Access support and your permission. Local HLS preview also requires compatible media playback.
Usage limits	Processing capacity depends on duration, dimensions, codecs, settings and available device memory. Large inputs can fail; keep the original file.
Which output quality does the HLS package include?	Choose an output preset before creating the package. Each preset writes a different set of video renditions, and the preview lets you switch between them.