Files
What happens to a file between upload and playback
Upload Setting
Open Admin → Setting → Files → Upload Setting to set limits and processing rules for uploaded files.
To choose where finished files are stored, use Admin → Setting → Files → Storage Setting. See Storage for storage servers and destinations.
Upload rules can differ by file type and purpose. Review the relevant Image, Video, Audio, or Subtitle group before changing a limit for your whole website.
Background Processing
Converting video or encrypting media can take longer than an upload request allows. With Background Processing enabled, the upload finishes first and your cronjob processes the file afterward. The file is not playable until processing completes. Keep your server cron running if you enable this option.
Check Admin → Setting → Cronjob → Run logs when a file remains unprocessed.
Chunk upload
Chunk upload sends a large file in smaller pieces that are joined on your server. It can help on slow connections; set the chunk size below your server’s upload limit.
Image rules
The Image group controls accepted formats, file size, dimensions and resizing. Resizing makes copies for different display sizes. Animated GIFs decides whether animated GIF uploads are accepted (added in v2.0.78). If you enable WebP output, see WebP for its prerequisites.
Video rules
The Video group controls accepted formats, size and width limits, conversion, lower-quality copies and optional HLS encryption and file protection. Conversion and HLS need working FFmpeg settings; see FFmpeg.
Audio rules
Set accepted audio formats, file size and minimum bitrate in the Audio group.
Waveforms are not made here: they come from the separate audiowaveform tool. See Audiowaveform.
Protect files keeps audio in a private folder on your server: Off, premium ( priced ) files only, or all files. See File Protection before enabling it.
Preview for premium files creates a free preview of priced audio when its required processing option is available.
Lower quality: Script can use FFmpeg to lower quality of uploaded audios to 256k, 192k, 128k, 64k
HLS Encryption prepares audio for in-app playback rather than direct playback of the original file. See the HLS section below for the download trade-off.
File Storage
Use Storage Setting to route files to your server or to supported FTP and S3-compatible storage. Configure the storage server first, then choose which uploads should use it. See Storage.
You can route different media and image types to different storage destinations. Check the destination and available space before changing an active upload workflow.
File Protection
RKHM can keep media files in a private folder that is only reachable through short-lived links, and can encrypt audio and video with HLS. Both are set in the Audio and Video groups of Upload Setting; how protected files are sent to visitors is chosen in the Protected files group.
Which setup to pick, how each one works with third-party storage, downloads and offline playback, and what no protection can prevent is explained in File Protection.
HLS encryption
HLS turns a media file into small pieces for streaming. When encryption is enabled, the player also needs a key to play those pieces. Configure FFmpeg first and test playback with an account that should have access.
The HLS Encryption setting is in the relevant Audio or Video group under Upload Setting. Encrypted output is for playback in your website’s player; it is not a normal file download.
If you also want to offer a file that can be played outside your website, use the corresponding Keep real files for download option. Keeping both versions uses more storage. Check your role and source download permissions separately.
File removal
When you remove an item, check Admin → Setting → Files → File List if you need to confirm what files remain. Shared files can still be in use by another item.
Empty folders may remain after files are removed.
File cleaning
Uploads pass through temporary storage before processing and moving to their final destination. An interrupted upload or failed background job can leave temporary files behind. The File Cleaner cron job (enable it under Setting → Cronjob → Setting) removes unused files and clears these temporary folders for you.
If a file does not appear where expected, check File List, Run logs and your storage settings before uploading it again.