What we built
We built a custom rich text editor widget inside a Foundry Action Form that lets users write a description with inline images. When the action is submitted, the full HTML is stored in a description field. The widget works as expected on the surface.
The issue
The HTML stored in the description field embeds images as base64 strings directly inside the markup. This creates a hard blocker for any downstream usage:
-
AIP Logic can’t process it — the raw HTML with large base64 blobs is too heavy and unstructured for a language model to meaningfully analyse or act on the description content
-
External applications can’t consume the images — downstream systems expect image URLs or binary references, not raw base64 strings embedded inside an HTML field
-
Image-based analysis is blocked — images can’t be piped to vision models, OCR, or classification pipelines because they aren’t discrete objects; they’re buried inside the HTML string
Has anyone run into this and found a clean workaround or a platform-level solution? Is there a recommended way in Foundry to handle images inserted via a rich text editor in Action Forms so they’re stored as proper references rather than inline base64? Any guidance or feature pointers would be appreciated.