Hi, @brenton. Let’s take a look at that base 64 encoded image data:
Below I am using the
base64 command line tool to decode that text:
$ echo 'dmVyc2lvbiBodHRwczovL2dpdC1sZnMuZ2l0aHViLmNvbS9zcGVjL3YxCm9pZCBzaGEyNTY6MzJjOTAwODM1N2M3NDUyYmJmMDEwYmRhYzRiM2NhMDI2MTA0ZGZhOTlhZDJjM2U0NjcyNTQ2MDkwZDQwOTk2NQpzaXplIDcxNzE1NAo=' | base64 --decode
The output above is the last three lines. If you are familiar with Git LFS you will recognize those as a Git LFS pointer:
Based on this, it seems clear that your site build is attempting to embed images as base64 encoded text into the HTML during the site build. This is a common practice and many static site generators do this. However, this is a “build time” image transformation and Large Media is incompatible with build time image transformations.
Quoting the Large Media documentation section on limitations, it says the following:
- 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.
To summarize, your site’s build is doing build time image transformation (the base 64 encoding is a transformation of the image) and this won’t be possible with Large Media.
The solutions for this are to stop doing the build time image transformations or to remove the Large Media add-on from the site.
Note, you can do build time image transformations with third-party Git LFS services - it just doesn’t work when Large Media is used.
If there are other questions or if you want to disable Large Media (and, if so, please read this support guide first), please let us know.