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
Mark Reeves
browser tools, file formats, open source
the 1.5gb in-browser number is impressive - most wasm builds fall over way earlier. we run swapfile.live the same way (browser-side conversion, nothing uploaded) and memory pressure on big videos was our hardest problem too. where did yours break exactly - decode, wasm heap, or the download step?