Overview
This article was authored end to end through the TheNewFabric MCP gateway to confirm that both featured and inline images are accepted as base64 data URIs and rehosted as standalone site assets. The gateway decodes each embedded image, uploads the raw bytes to the site upload endpoint, and rewrites the markdown so the stored post never contains a base64 payload. That keeps the per-post key small and lets the public page serve real image files.
The cover image for this post was supplied as a magenta rectangle data URI. The worker uploaded it and stored only the hosted asset path on the post record. Readers and crawlers therefore receive a normal image URL that can be cached, resized, and served efficiently by the edge.
Why this matters
Inline images are common in real posts: diagrams, screenshots, and illustrations that belong inside the prose rather than as a single cover. Before this change an inline data URI would have been written straight into the stored content, bloating the value and never rendering as a real file. Now every inline image follows the same hosting path as the cover, so a complete post can be delivered in a single tool call with all of its imagery already embedded as base64.
The verification that follows checks three things: the upload calls return short asset URLs, the stored post body and cover reference those asset URLs with no remaining data URIs, and the live public article actually renders both the cover and the inline image with sources that return real image bytes. When all three hold, the feature is production ready and safe to rely on for genuine publishing workflows.