Download an Article as a File

Open Publish in the writing workspace and switch to the Download tab, then choose Doc, PDF, HTML, or Markdown. This is the route to use when your platform has no integration or somebody else publishes for you.

Last updated 1 day ago

Exporting a copy is the manual alternative to publishing through an integration. The panel describes it plainly: "Export a copy if you want to publish manually."

Steps

Open the article in the writing workspace.
Select Publish in the title bar.
Switch to the Download tab.
Choose a format: Doc, PDF, HTML, or Markdown.

You will see a confirmation such as "Doc download started".

Which Format to Choose

Format	Use it for
Doc	Sending to a client or editor for review and comments
PDF	A fixed copy for approval or records
HTML	Pasting into a CMS that has no integration
Markdown	Static site generators and developer workflows

Doc

The right choice for review. Anyone can open it, and it keeps track changes and comments available in the tools your reviewers already use.

PDF

Layout is fixed, which is what you want for sign-off and what you do not want if the recipient needs to edit.

HTML

Preserves headings, links, lists, and tables, which is exactly what survives a paste into most editors. If your CMS is unsupported, this is usually the least lossy route.

Check how your editor handles the paste. Some strip attributes and some rewrite the markup, so it is worth a test before you build a workflow on it.

Markdown

Plain text with structure intact. The right format for anything Git-based, and the most durable if you want a copy that will still be readable in ten years.

Notes

Downloading costs no credits.

Downloads include the article body. Your SEO title and description live in the SEO tab, and are worth copying separately if the destination needs them. Each meta field has a copy control.

Images in a download are referenced rather than embedded for the web formats, so if you are moving to another system you may need to handle images separately.

Downloading does not change the article's status in NarraSEO. It stays as it is in your Documents list.

When Downloading is the Right Answer

Your platform is not supported. Thirteen CMS platforms have integrations, which leaves plenty that do not.

Somebody else publishes. If your client or a colleague owns the CMS, sending a Doc is simpler than getting credentials.

Your CMS is heavily customised. Custom post types, unusual field structures, or a bespoke build can be easier to handle by hand.

You need an approval trail. A PDF sent for sign-off is a record.

You only publish occasionally. Setting up an integration for one article a quarter is not worth it.

When to Use an Integration Instead

If you publish regularly to a supported platform, the integration is worth the setup. It preserves formatting reliably, handles images, sends metadata, and gives you draft and scheduled statuses. The setup is paid once.

How publishing works covers both routes. Publishing an article to your site covers the integration route in detail.