Images changed encoding to base64

Hi guys,
All of a sudden, all image url got encoded as base64 which (1) make them unreadable and unmatchable to Google sheets and (2) make the app slow. Have you experienced it? How can we resolve it?


Can you post a screen shot please? Is the URL string being changed on existing rows in your old data? Or only on new rows as they are saved?

1 Like

Thank you for the response! Previously, the values were saved as normal human-readable - see the first row while nowadays everything is saved in base64. No changes were done but I was told by the team that Appsheet changed how it saves the images, so I wondered if it is true.

1 Like

@Ekaterina_Ponkratova, where are these images being saved from? Are they taken on a mobile device and uploaded via the AppSheet mobile app?

@Aleksi, do you know anything about a change to how images stored?

The images are loaded from the app front-end - Appsheet and saved in a google driver folder. The data is saved in a mysql database.

1 Like

Please post a screenshot of the app’s column configuration.

Thank you, Steve, for the response:

The app’s column configuration, please.

1 Like

1 Like

Thanks for the screenshots! I see nothing wrong with them.

The behavior you’re experiencing is definitely odd–I have no explanation for it. I’m going to have to refer you to for further help here.

Please let us know here what the problem turns out to be!

Thank you, Steve. That’s precisely I find weird as nothing was changed.

1 Like

This indicates we were unable to save the image to a file in your file storage, saving the data to the sheet instead is a fallback behavior to try to avoid losing the image. If the row is edited again it should cause the system to retry to save the image.

Most of the time the reason for failure to save the file is insufficient space in Google Drive, if you see this happening that would be the first thing to check.

We’re considering whether to handle this differently since it’s unexpected and confusing to see the image data show up in the cell. And if we detect insufficient drive space we should communicate that back to the app owner.


Hi Adam,

Thank you for the response! I am confirming with the Driver owner because the storage is like 20% full but it is unclear if at the moment of failure, there was a storage issue. Let’s assume that the storage size was increased and now all the images are saved as jpg not as base64. How should we handle those that came out as base64? Re-submit them?

Warm regards,