I have updated the plugin and tested by clearing cache, but unfortunately I still see the same issue. SVG is not converted to webp(png) as you can see in here:
Anyway, if you could let us decide image types selectable, that would definitely solve this issue tho. Can you implement this feature like the Picture uploader can restrict image types to upload? (but the feature does not solve the issue unless you exclude SVG completely.)
Thank you and your engineering team for your efforts in tackling this issue.
Hello @rio,
We hope this message finds you in good spirits.
I have updated the plugin and tested by clearing cache, but unfortunately I still see the same issue. SVG is not converted to webp(png) as you can see in here:
Yes we understand that it is frustrating to deal with the way Bubble processes SVG files, we asked our devs to look once more if the set-up from the test page you shared with us is possible to adjust to avoid issues with SVG format and they informed us of the fact that:
When using Image Compressor, it’s important to note that SVG files are recognized as XML files with the mime type “image/svg+xml” by browsers. This can cause certain display or compatibility issues.
maybe this isn’t relevant to my issue, but worth mentioning if you find it useful.
Well you can experiment with Imgix also but take into account that Bubble has its specific limitations, we are doing our best to help you, but unfortunately, we cannot change how the
Svg file gets seen by browsers.
Anyway, if you could let us decide image types selectable, that would definitely solve this issue tho. Can you implement this feature like the Picture uploader can restrict image types to upload? (but the feature does not solve the issue unless you exclude SVG completely.)
Thank you for the suggestions, we will check if it’s feasible and if the plugin library allows us to implement these changes - we will notify you once there are any updates but can’t provide any timeframes.
Thank you very much for you patience and understanding through this process.
Best regards,
Zeroqode Support Team
Uncompressed base64 is only for regular images but not for SVG ??
No worries, we are glad to help and make things clearer. Some context should be offered so that the plugin’s logic will be clearer.
Uncompressed base64 encoding is typically used for regular images like JPEG, PNG, or GIF because these formats are inherently binary data that need to be encoded to be included in HTML or CSS files.
It works perfectly fine by simply selecting compressed base64 , but Not a Uncompressed64.
SVGs, on the other hand, are text-based XML files that describe images using vector data. Since SVGs are text files, they can be directly embedded or included without the need for base64 encoding.
Using uncompressed base64 encoding for SVGs is unnecessary and can increase file size, making it less efficient.
I hope this clarifies why uncompressed base64 is only recommended for regular images and not for SVGs. If you have any further questions, feel free to ask!
Best regards,
Zeroqode Support Team.
Where is the workflow EVENT for Compressor Uploaded MULTIPLE to S3 so I can continue the workflow after this event, however the only action there is for a single Upload to S3.
Hi, this is similar to NicolasMM’s question above, which does not appear to have been answered:
I’ve read the documentation and this thread, and I’m throwing up errors after the transform and upload (and changes) shown below. Any ideas what needs to change?
Thanks for reaching out to us, we have already discussed via email previously and will write here as well to make sure you will see the message.
For your use-case, when you use the action “Upload multiple to S3”, you can use the event “Done multiple uploads” to know when the files are successfully uploaded and to continue your workflow from there.
Could you please give it a try and let me know if everything is working fine for you? If you will have any further concerns, please share more details such as screenshots or a screencast of how you set up the workflows, plugin element, and the problem you’re experiencing.
From the images you provided, it appears that you’re selecting, uploading, and saving to the database all within the same workflow. This could lead to problems, as the states you’re referencing may not yet be available at the time of the action.
To avoid this, we recommend using the plugin events “Done Compression” and “Image Uploaded” to ensure the file has fully compressed or uploaded before proceeding to the next workflow action.
Introduced pre-signed URLs for AWS S3 uploads to keep your keys private and minimize risk.
The pre-signed URL includes permissions and an expiration time, allowing secure and time-limited access to the specified file without exposing sensitive AWS credentials. It is commonly used for uploading files directly to S3.
Please refer to the plugin documentation for more details.
Update to the latest version (3.34.0) now for a more secure experience!
Thanks for the plugin! I have a list of images already stored in my database, and I’d like to use your plugin to reduce their size and then save the new compressed images back to the database.
Is it possible to use existing image URLs for this process? On your demo page, the URL image example doesn’t seem to be working—it doesn’t display either the original or the compressed image.
Could you please confirm if the plugin supports compressing images already stored via URL, and how I might accomplish this?
We are glad you’re finding it useful! We totally get wanting to compress your existing images stored in the database via URLs and save the new versions back. Let’s tackle your questions and get this working for you.
Can You Compress Images from URLs?
Good news—yes, the plugin does support compressing images from existing URLs! According to the Image Compressor and Uploader documentation, there’s a “Compress from URL” action that lets you do exactly this. You can take an image URL from your database, compress it, and then save the compressed version back.
About the Demo Page Issue
You mentioned the URL image example on the demo page isn’t working—it’s not showing the original or compressed image. I can confirm there was a recent issue with Heroku that affected the demo page, but I’m happy to let you know it’s been fixed now! You should be able to see the demo working as expected.
How to Compress and Save
Here’s a simple way to set this up in Bubble:
Add the Image Compressor and Uploader element to your page if you haven’t already.
In a workflow (e.g., when a button is clicked or for each image in your list), use the “Compress from URL” action.
Set the URL field to your image URL from the database (e.g., Current cell’s Image URL).
Once the compression is done, the plugin will trigger an “Image Compressed” event—use this to save the compressed image data to your database in the appropriate field.
A Few Things to Check
To make sure it works smoothly:
Direct URL: Make sure the URL is a direct link to the image (e.g., ends with .jpg or .png), not a webpage.
Public Access: The image needs to be publicly accessible without login requirements.
Cross-Origin Access: Some domains block cross-origin requests, which can stop the compression. Try using an image from a public source like Unsplash or Flickr to test. The plugin has fixed some cross-origin issues recently, but it’s still worth checking.
If you’re still having trouble, the documentation has more details on setup.
Give this a try and let us know how it goes! If you’re still seeing issues with the demo or need help with the workflow, We are happy to dig deeper.
I noticed the plugin has a state and workflow when the user selects multiple files (A Compressor Multiple selected).
Is it possible to add a state and workflow when the user selects only one? I’m using the Select and Compress action, then the Upload image action. This whole flow can take a few seconds for larger images such as .HEIC, so I would like to display a loading element when the user selects an image if possible.
Thanks for the kind words, and we’re glad to hear you’re enjoying the plugin!
We absolutely agree that adding a state or workflow for when the user selects only one file would be a great feature, and we’ll definitely pass this idea along to our development team for consideration in future updates.
However, if you’d like to have this feature implemented sooner, you can submit a request through our Paid Development Request Form, where we can prioritize custom features for you.
Let us know if you have any other questions or if there’s anything else we can assist with!
I also noticed that HEIC pictures taken from an iPhone 16 Pro Max, then sent to a computer, then uploaded to Bubble from that computer, using the Select and Compress then Upload image actions, somehow are not getting uploaded. This flow always works great with pictures taken with other iPhone models. Not sure if it’s a bug or a limitation?
Below is an example picture so you can try and reproduce on your end
