Repository navigation
[bug]: Export Page Content Error - Failed to convert image to base64 #6221
Description
Is there an existing issue for this?
- I have searched the existing issues
Current behavior
When I do export a page content, it's only contain text. Console show message Failed to convert image to base64 while image url (private storage) actually is:
https://{hostname}/api/assets/v2/workspaces/{slug}/projects/{projectId}/ce2efef3-9ccb-4a10-85b9-5bc0c012581e/
Markdown syntax also doesn't has any url inside even I export as Markdown or Copy Markdown
Steps to reproduce
- Go to Pages
- Export a page to PDF
Environment
Production
Browser
None
Variant
Self-hosted
Version
v0.24.1
Metadata
Metadata
Labels
Type
Fields
Edition
None yet
Version
None yet
Activity
aaryan610 commentedon Dec 18, 2024
Hey @isrealbm, thanks for bringing this up. This issue has already been reported, and our team is actively working on pushing a fix for it.
aquantech commentedon Dec 18, 2024
By the way, can you add Table of Content on the top of page's content?
jfriboldi commentedon Jan 28, 2025
Any news on this? It also doesn't work on cloud version.
bhavyasaraswat2208 commentedon Feb 4, 2025
@jfriboldi Thanks for the response and your patience, our team is actively working on it for a seamless fix.
fnellen commentedon Jun 25, 2025
Unfortunately, the issue still persists: exporting with images is still not working. The Markdown export also doesn’t include any links to the images.
This is our current installation: v1.11.0 in Swarm mode.
This is the errormessage shown in the console:
csipapicsa commentedon Jan 20, 2026
is there any update about it?
Palanikannan1437 commentedon Jan 21, 2026
Hey @csipapicsa, yess, very soon and we now have much better exports too in pages, exporting all supported nodes in a much better way and some perf improvements along the way too :p
here's the pr -> #8564
sriramveeraghanta commentedon Sep 7, 2026
Hi @aquantech, @fnellen, @jfriboldi, @csipapicsa — thanks for your patience on this one, and for the detail in the reports (the exact error strings and the asset URL shape were genuinely useful).
Page export has been reworked rather than patched. As @Palanikannan1437 mentioned above, #8564 replaced the old client-side export with a server-side renderer in the live service, which removes the browser-side base64 conversion step that was producing:
That conversion was the root of the problem — it validated the asset
srcwithnew URL(...), which throws on the relative/api/assets/v2/workspaces/...paths used when the web app and API are served from the same origin. The new exporter resolves assets server-side instead, and also handles a much wider set of nodes with better fidelity.This is resolved in the latest commercial edition, so I'm closing this out.
If you're on a current version and still hit missing images on export, please open a fresh issue with your version, edition, and deployment shape (and the console error, if any) — that'll be much easier to act on than continuing here.
@aquantech — on your table-of-contents request: that's a separate feature ask, so it won't be tracked by this issue. Worth opening as its own request so it can be triaged properly.
Thanks again, all. 🙏