Hi, @tdelgio, I’m seeing both deploys service the LFS files correctly:
both send identical content when I test.
It might help to know exactly what URL isn’t working. From @gregraven’s reply it sounds like the missing files are being embedded into the HTML as base64 encoded binary data (binary data encoded as text).
Here is an example from the index.html file:
<source src="data:video/mp4;base64,dmVyc2lvbiBodHRwczovL2dpdC1sZnMuZ2l0aHViLmNvbS9zcGVjL3YxCm9pZCBzaGEyNTY6YjYzYjA2YzI1N2RkNzYzOTM5YzliNDUyMGQxNzc5NmE3ZjY3MGM1ZjE4Y2NlOTY4NTFlODJhMzRjOWEyZWQ4MgpzaXplIDEwMDc0MTQK" type="video/webm"/>
If you decode the text, you will see a Git LFS pointer instead of the video file:
$ echo "dmVyc2lvbiBodHRwczovL2dpdC1sZnMuZ2l0aHViLmNvbS9zcGVjL3YxCm9pZCBzaGEyNTY6YjYzYjA2YzI1N2RkNzYzOTM5YzliNDUyMGQxNzc5NmE3ZjY3MGM1ZjE4Y2NlOTY4NTFlODJhMzRjOWEyZWQ4MgpzaXplIDEwMDc0MTQK" | base64 --decode
This happens because the binary video data is required during the site build so it can be encoded and that isn’t possible with Large Media. Only the pointer is downloaded and the pointer, not the file is being encoded.
This is covered in the Large Media requirements and limitations documentation here, quoted below:
- Files tracked with Large Media are uploaded directly to the Netlify Large Media storage service on push, completely bypassing the site build. This saves build time, but also means that the files are not available to tools that process asset files during the build, such as Hugo’s image processing or the
gatsby-image plugin. Depending on your needs, you may be able to replace this functionality with Netlify’s image transformation service.
If you need to embed the video in the HTML, you can use Git LFS but not Large Media. If you need to make changes to this site because if this (for example, removing the Large Media add-on), please let us know.