Download the Text Editor’s current rich document as a structured DOCX, standalone styled HTML page, PDF, or Markdown without discarding images, tables, alignment, colors, or rich-only content.
Where: Flowgen Text Editor → open the fullscreen editor → download controls in the top bar
Key ideas
- Rich source first: HTML, Word, and PDF start from richHtml when present and fall back to rendered Markdown. A document made only of rich content can still export even when the Markdown string is empty.
- Real Word structure: DOCX export maps headings to Word heading styles, nested lists, tables with header rows, links, embedded images, and paragraph alignment into OOXML instead of pasting a screenshot or plain text.
- Standalone web document: HTML export includes a doctype, charset, responsive page measure, typography, dark-scheme styling, and RTL-aware rules rather than saving an app-only body fragment.
- Four distinct outputs: Markdown preserves the portable source; HTML preserves web formatting; DOCX is editable in Word-compatible apps; PDF is the fixed-layout sharing output.
Steps
- Open the Text Editor fullscreen and review the document in Rich mode; use Markdown mode only when you need to correct the source.
- Set a clear document title because it becomes the download filename and the title inside rich exports.
- Choose Markdown, styled HTML, Word (.docx), or PDF from the top-right download controls.
- Open the downloaded file outside flowmo and verify headings, lists, tables, links, images, direction, and page breaks.
- If an image conversion warning appears for Word, inspect the affected image and retry after replacing an unsupported or oversized source.
Image handling in Word
WebP, AVIF, and oversized raster images are converted through the browser to PNG or JPEG when Word cannot embed the original format directly. The export reports a warning instead of silently omitting the image.
Direction detection
The standalone HTML/PDF document uses majority-based RTL detection, so one quoted Hebrew or Arabic line does not flip an otherwise left-to-right report.
Rich-document input and editing fixes
PDF and Markdown briefs reach the model through the attachment-preparation path. The text editor defaults body copy to Arial, Find no longer steals the editing caret, and repeated-update failures are corrected. Export still uses the rich document where available rather than discarding images, tables, or formatting.
Limitations and important notes
- Word-compatible applications can render fonts and page breaks differently.
- Markdown cannot preserve every rich-only style, table behavior, or embedded image treatment.
- Remote images must be fetchable by the browser to be embedded into a DOCX.
Troubleshooting
The Word export has no image
Check the export warning, confirm the source URL is accessible to the browser, and replace a blocked/unsupported source before exporting again.
The HTML file looks different from the editor
Confirm you used Download a styled web page, then inspect custom fonts or remote media that may not be available outside the app.