Croppie plugin – “Result image” not saving correctly to Bubble DB

Need help
1

Hello,

I’m using the Croppie plugin (by Misha V) in my Bubble app to let users upload and crop an image before saving it to the database.
However, I’m facing an issue where the cropped image (Result image) is not being saved to my database field as expected.

Here’s my setup and what’s happening:

:puzzle_piece: Current setup

  • Plugin: Croppie (free version by Misha V)

  • Dynamic image source: PictureUploader_new's value

  • Output format: png

  • Size: viewport

  • Workflow:

    1. Step 1: Save Croppie A

    2. Step 2: Create a new “Children” record

      • icon = Croppie A's Result image

    3. Step 3: Hide popup

:warning: Issue

  • When I trigger the workflow, the Children thing is created,
    but the icon field (image type) remains empty.

  • The Croppie preview works fine (cropped area is displayed correctly).

  • It seems that the “Result image” is still in Base64 format, and not a valid Bubble file object or URL.

  • I tried calling “Save Croppie A” before creating the record, but the timing might be asynchronous (the Result image isn’t yet ready when the record is created).

:magnifying_glass_tilted_left: What I’ve tried

  • Checked Dynamic image = PictureUploader_new’s value:processed with Imgix

  • Disabled “Attach file to thing type” (left blank)

  • Output format = PNG / Size = viewport

  • Tried using “Save Croppie A” → “Upload file” workflow (but “Upload file” doesn’t seem to recognize Base64 directly)

:red_question_mark: Questions

  1. Does the free Croppie plugin actually output a file URL or only a Base64 string in Result image?

  2. Is there a recommended way to convert the Croppie result into a proper Bubble file that can be stored in an “image” field?

  3. Is the “Save Croppie A” action asynchronous? If so, how can I trigger a DB create action after the save is complete?

  4. Should I use the paid version (Croppie Extended) to properly store cropped images in Bubble’s file storage?

Thank you very much for your help — I’d appreciate any guidance or a working example of how to correctly save the cropped image to Bubble’s database.

Best regards,

Mitsuharu

2

Hey @macromitsuhall, Yeah, that happens with the free Croppie plugin, it only returns a Base64 string, not a real Bubble file, so it won’t save directly to your image field.

You’ve got two options: Use a backend workflow or the “Upload data as file” API call to convert the Base64 into a proper file URL before saving or go with Croppie Extended, which handles that part automatically.

Also, “Save Croppie” runs asynchronously, so try adding a tiny delay or run the “Create new record” only after the result image isn’t empty.

I’ve run into this before, happy to show how to set it up cleanly if you want.