Visual Bugs in Payload CMS when Displaying Embedded Images from MongoDB about payload HOT 2 CLOSED

Storing images in MongoDB is not recommended by Mongo. I would say this is something that we are unlikely to address, especially since Payload has dedicated upload functionality that can be leveraged.

from payload.

Storing images in MongoDB is not recommended by Mongo. I would say this is something that we are unlikely to address, especially since Payload has dedicated upload functionality that can be leveraged.

I am currently working on a project involving an image similarity search engine. In this project, each image undergoes processing through the SIFT algorithm to obtain its descriptor, represented as an array. Subsequently, the descriptor is converted into a base64 string. The reason behind this conversion is to streamline the storage process in MongoDB, as directly storing the descriptor without conversion results in significantly increased storage requirements. Essentially, this descriptor serves as a compact representation of the image. The actual images are stored in a Cloudinary Content Delivery Network (CDN), while MongoDB stores only the corresponding Cloudinary URL along with the converted string that represents the image. The image search algorithm operates by taking an image descriptor and seeking matches within the database's embeddings. To clarify, the images themselves are hosted on the CDN rather than in MongoDB; MongoDB solely manages the storage of the image embeddings, which are lengthy strings. Please reconsider this issue, as it does not have any connection to image uploading. The problem likely occurs when the CMS tries to display a very, very long string.

from payload.