[Feature Request] Add file size limit / warning when dropping large video files

[CodeWizard0909]

Overview

Reframe is an offline, in-browser video editor, so all processing happens on the client side. Currently, there is no visible file size limit on the video drop zone users can import very large files without any warning or restriction. This can lead to browser freezes, crashes, or extremely slow performance on devices with limited memory or weaker CPUs.
Adding a clear file size limit and user feedback around large files would improve stability and UX, especially for users on low–mid range machines.

Current Behavior

1. The drop zone accepts video files of any size with no validation
2. No file size is shown after a file is selected
3. No warning or error is displayed for oversized files

Expected Behavior

1. Display the file size after a video is dropped using the existing formatBytes utility
2. Show a warning if the file exceeds a defined threshold (suggested: 2 GB)
3. Optionally block processing entirely above a hard limit with a clear error message

Acceptance Criteria

[ ] File size is displayed once a video is loaded
[ ] A warning is shown for files exceeding the defined threshold
[ ] Uses the existing formatBytes utility (see #231)
[ ] No regression to existing drag-and-drop or file input behaviour

I am a GSSoC 2026 contributor and I'd love to work on this issue. Could you please assign it to me?

[indresh404]

@magic-peach Hi, I would like to work on this issue under GSSoC 2026.

[KhushiVadadoriya]

@magic-peach Hi! I’m a GSSoC 2026 contributor and I’d like to work on this issue. The task looks beginner-friendly and I’m interested in improving the user experience around large file handling and validation. Could you please assign this issue to me?

[aucxtix]

Hi @magic-peach, I have a clear plan to implement the file size validation and UX improvements for Reframe as outlined in above issue.
Could you please assign this issue to me so I can begin working on the pull request for GSSoC 2026?

[Adrija-dotcom]

Hi, I would like to work on this issue under GSSoC 2026. Could you please assign it to me?

[magic-peach]

@CodeWizard0909 will be assigned the issue since they asked first and created it but the other contributors are free to check out the other issues

[TanviHanda]

Hi @magic-peach , I would like to work on this issue.

I’ve reviewed the requirements and plan to:

• display the uploaded file size using the existing formatBytes utility
• add warnings for oversized files
• ensure there is no regression in the current drag-and-drop/file upload flow

Could you please assign this issue to me?

[Aman-jha12]

Hi @magic-peach I would like to contribute on this issue and fix it asap

[deepikamishra25]

Hi @maintainer,
I would like to contribute to this project under GSSoC 2026.
Could you please assign this issue to me?

[Pranav-IIITM]

Hi @magic-peach, I’m a GSSoC’26 contributor and would love to collaborate on this issue with the assigned contributor if possible. Please let me know if collaboration is allowed.

[naitikrt678]

Hi @magic-peach , I'm a GSSoC 2026 contributor and would love to work on this.

[Dhruva5vora]

Hi @magic-peach 👋

I’m a GSSoC 2026 contributor and I’d love to work on this issue.

I have experience with React, JavaScript, and frontend development, and I understand the requirements:

• Display the uploaded file size using the existing formatBytes utility
• Show a warning for files larger than the defined threshold
• Ensure existing drag-and-drop and file input behavior remains unchanged

This looks like a meaningful UX improvement, and I’d be happy to implement it.

Could you please assign this issue to me? Thank you!