I'm writing a client-side upload script that pre-chunks the input data before sending.

I was just wondering if this could potentially lead to a huge memory spike, calling the slice method on the potentially very big File (e.g., slicing a 2GB file into 1000x2MB chunks) before starting the upload, as opposed to slicing it just before each chunk upload starts.

I figured the browser is not actually handling the data with the slice method, it's just returning a new instance of Blob with a different start and end range, but I just want to be sure.

I know it's easily testable but I'm not sure if I can trust a test result on Chrome would apply to all browsers.