1.5GB entirely in-browser is impressive, curious how you're managing memory for that in ffmpeg.wasm since I've seen tabs just crash on much smaller files once the wasm heap fills up. did you have to chunk the processing or does WebCodecs handle enough of the heavy lifting to avoid that
Regarding the limitation of the 32‑bit WASM heap! Breaking it down into fragments using File.slice is what’s needed, and it’s important to optimize backup paths. Thank you for your questions!
Tarun Sharma
React.js Frontend Web Developer | Next.js Specialist
1.5GB entirely in-browser is impressive, curious how you're managing memory for that in ffmpeg.wasm since I've seen tabs just crash on much smaller files once the wasm heap fills up. did you have to chunk the processing or does WebCodecs handle enough of the heavy lifting to avoid that