Export to rst, odt or docx #1039

New Issue

OVERLORD · 2026-02-04T23:33:09+03:00

OVERLORD commented

2026-02-04 23:33:09 +03:00

Originally created by @lindesbs on GitHub (Feb 13, 2019).

Describe the feature you'd like
PDF, HTML and txt export are quite fine, but we have an internal design definition, which depends on docx. So it would be fine to export to other formats like rst, docx or odt

Describe the benefits this feature would bring to BookStack users
much more usefull documents

Originally created by @lindesbs on GitHub (Feb 13, 2019). **Describe the feature you'd like** PDF, HTML and txt export are quite fine, but we have an internal design definition, which depends on docx. So it would be fine to export to other formats like rst, docx or odt **Describe the benefits this feature would bring to BookStack users** much more usefull documents

OVERLORD added the ☕ Open to discussion 🔨 Feature Request 🏭 Back-End labels 2026-02-04 23:33:09 +03:00

OVERLORD closed this issue

2026-02-04 23:33:12 +03:00

OVERLORD commented

2026-02-04 23:33:18 +03:00

@ssddanbrown commented on GitHub (Feb 13, 2019):

Hi @lindesbs,
Thank you for your request.

Exporting to other editable formats is quite a complicated process so I'd like to better understand your actual goal here.

What are you actually trying to achieve here? Your request dictates a specific implementation (Export to specific formats) but It'd be good to understand why you'd like this implementation. For example, are you intending to edit documents in a specific program? If so, why?

@ssddanbrown commented on GitHub (Feb 13, 2019): Hi @lindesbs, Thank you for your request. Exporting to other editable formats is quite a complicated process so I'd like to better understand your actual goal here. What are you actually trying to achieve here? Your request dictates a specific implementation (Export to specific formats) but It'd be good to understand why you'd like this implementation. For example, are you intending to edit documents in a specific program? If so, why?

OVERLORD commented

2026-02-04 23:33:23 +03:00

@lindesbs commented on GitHub (Feb 13, 2019):

Quite easy. 3 persons from our service desk would like to add docs or chapters depending our actual requirements. Additionally 5 developer add their parts and would like to enhance existing docs. So, many persons with different knowledge work on the same docs. Impossible for „word“. That’s why we use BookStack.
But we will still use our templates from the office app. Not adding a new pdf template to bookstack. Just want to export the content and import it into office or markdown etc.

@lindesbs commented on GitHub (Feb 13, 2019): Quite easy. 3 persons from our service desk would like to add docs or chapters depending our actual requirements. Additionally 5 developer add their parts and would like to enhance existing docs. So, many persons with different knowledge work on the same docs. Impossible for „word“. That’s why we use BookStack. But we will still use our templates from the office app. Not adding a new pdf template to bookstack. Just want to export the content and import it into office or markdown etc.

OVERLORD commented

2026-02-04 23:33:27 +03:00

@ssddanbrown commented on GitHub (Feb 13, 2019):

@lindesbs Okay. Word can open HTML files so you could export as a contained HTML file and open with word then edit as you please or re-save as docx.

@ssddanbrown commented on GitHub (Feb 13, 2019): @lindesbs Okay. Word can open HTML files so you could export as a contained HTML file and open with word then edit as you please or re-save as docx.

OVERLORD commented

2026-02-04 23:33:31 +03:00

@lindesbs commented on GitHub (Feb 13, 2019):

Maybe. I've cloned your repo and will prepare "my view" and report it.

@lindesbs commented on GitHub (Feb 13, 2019): Maybe. I've cloned your repo and will prepare "my view" and report it.

OVERLORD commented

2026-02-04 23:33:34 +03:00

@Nebucatnetzer commented on GitHub (Feb 14, 2019):

If this would get integrated I personally would just go with odt.
Simply because it's IMO the more open format.
rst seems to be a bit too specific in that case markdown would make more sense since that's one of the supported formats of Bookstack.

@Nebucatnetzer commented on GitHub (Feb 14, 2019): If this would get integrated I personally would just go with odt. Simply because it's IMO the more open format. rst seems to be a bit too specific in that case markdown would make more sense since that's one of the supported formats of Bookstack.

OVERLORD commented

2026-02-04 23:33:39 +03:00

@doenietzomoeilijk commented on GitHub (Feb 25, 2019):

@Nebucatnetzer Actually ("Ackshually..."), MarkDown is only supported if you set your content to use Markdown. If you set it to WYSIWYG, you can only export to text, HTML and PDF.

@doenietzomoeilijk commented on GitHub (Feb 25, 2019): @Nebucatnetzer Actually ("Ackshually..."), MarkDown is only supported if you set your content to use Markdown. If you set it to WYSIWYG, you can only export to text, HTML and PDF.

OVERLORD commented

2026-02-04 23:33:44 +03:00

@Nebucatnetzer commented on GitHub (Feb 25, 2019):

Ackshually, I know that ;p.
I meant that Markdown would make more sense then rst (and probably even plaintext) since Markdown is very close to HTML and it is already supported by BookStack.

Mon Feb 25 14:53:57 GMT+01:00 2019 Max Roeleveld notifications@github.com:

@Nebucatnetzer [https://github.com/Nebucatnetzer] Actually ("Ackshually..."), MarkDown is only supported if you set your content to use Markdown. If you set it to WYSIWYG, you can only export to text, HTML and PDF.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub [https://github.com/BookStackApp/BookStack/issues/1273#issuecomment-467018975] , or mute the thread [https://github.com/notifications/unsubscribe-auth/ACLmdRiv-j_LnGIJRJG2ysxV2efZABhVks5vQ-rzgaJpZM4a4_h-] . [https://github.com/notifications/beacon/ACLmdTSLYfWLazzophjLOc7xhW8YhfXOks5vQ-rzgaJpZM4a4_h-.gif]

@Nebucatnetzer commented on GitHub (Feb 25, 2019): Ackshually, I know that ;p. I meant that Markdown would make more sense then rst (and probably even plaintext) since Markdown is very close to HTML and it is already supported by BookStack. Mon Feb 25 14:53:57 GMT+01:00 2019 Max Roeleveld <notifications@github.com>: > > @Nebucatnetzer [https://github.com/Nebucatnetzer] Actually ("Ackshually..."), MarkDown is only supported if you set your content to use Markdown. If you set it to WYSIWYG, you can only export to text, HTML and PDF. > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub [https://github.com/BookStackApp/BookStack/issues/1273#issuecomment-467018975] , or mute the thread [https://github.com/notifications/unsubscribe-auth/ACLmdRiv-j_LnGIJRJG2ysxV2efZABhVks5vQ-rzgaJpZM4a4_h-] . [https://github.com/notifications/beacon/ACLmdTSLYfWLazzophjLOc7xhW8YhfXOks5vQ-rzgaJpZM4a4_h-.gif] >

OVERLORD commented

2026-02-04 23:33:47 +03:00

@numinance commented on GitHub (Apr 15, 2020):

Thanks for all your hard work @ssddanbrown

My first post in this project and just wanted to say I am really enjoying this software and am really keen to introduce it across my company as the primary documentation management source.

Currently the below process works as a substitute for native .ODT,:

Export the BookStack Book to html
Open LibreOffice Writer with the chosen template (ie with styles)
Use "import text" to import the html file into the LibreOffice Writer template

This seems to work well enough, but has some issues with spacing etc that I am still figuring out. In the meantime, are there any current plans for exporting ODT, DOCX or LaTeX formats?

@numinance commented on GitHub (Apr 15, 2020): Thanks for all your hard work @ssddanbrown My first post in this project and just wanted to say I am really enjoying this software and am really keen to introduce it across my company as the primary documentation management source. Currently the below process works as a substitute for native .ODT,: 1) Export the BookStack Book to html 2) Open LibreOffice Writer with the chosen template (ie with styles) 3) Use "import text" to import the html file into the LibreOffice Writer template This seems to work well enough, but has some issues with spacing etc that I am still figuring out. In the meantime, are there any current plans for exporting ODT, DOCX or LaTeX formats?

OVERLORD commented

2026-02-04 23:33:51 +03:00

@ssddanbrown commented on GitHub (Apr 26, 2020):

@numinance

Thanks for all your hard work

Thanks!

In the meantime, are there any current plans for exporting ODT, DOCX or LaTeX formats?

Not really to be honest. I like the idea of exporting to ODT but it's quite a different format, and the implementation would likely spawn a wave of additional issues or option requests so it's not something I'd be looking to support in the near future. I'd be surprised if we could get many close to better formatting than LibreOffice to be honest.

For now, here's a couple of things that might help if you're not already aware of them:

Libreoffice can be ran via command line to convert files like below. Just an option if you want to script something to convert many files. Not sure if you can merge styles with an existing doc though.

libreoffice --headless --convert-to odt code-page.html

PanDoc is another option for converting files. Can convert from HTML to a pretty wide range of options. Might be worth seeing if it's ODT format gets you closer.

@ssddanbrown commented on GitHub (Apr 26, 2020): @numinance > Thanks for all your hard work Thanks! > In the meantime, are there any current plans for exporting ODT, DOCX or LaTeX formats? Not really to be honest. I like the idea of exporting to ODT but it's quite a different format, and the implementation would likely spawn a wave of additional issues or option requests so it's not something I'd be looking to support in the near future. I'd be surprised if we could get many close to better formatting than LibreOffice to be honest. For now, here's a couple of things that might help if you're not already aware of them: * Libreoffice can be ran via command line to convert files like below. Just an option if you want to script something to convert many files. Not sure if you can merge styles with an existing doc though. ```bash libreoffice --headless --convert-to odt code-page.html ``` * [PanDoc](https://pandoc.org/) is another option for converting files. Can convert from HTML to a pretty wide range of options. Might be worth seeing if it's ODT format gets you closer.

OVERLORD commented

2026-02-04 23:33:57 +03:00

@A9G-Data-Droid commented on GitHub (Apr 16, 2024):

Quite easy. 3 persons from our service desk would like to add docs or chapters depending our actual requirements. Additionally 5 developer add their parts and would like to enhance existing docs. So, many persons with different knowledge work on the same docs. Impossible for „word“. That’s why we use BookStack. But we will still use our templates from the office app. Not adding a new pdf template to bookstack. Just want to export the content and import it into office or markdown etc.

This workflow you are describing is the ideal use case for Editing a shared Word doc in M365. You upload the file to a SharePoint site, which is also the backend for Teams and OneDrive so it works there too. Then you can see everyone editing the document live. It's wild. Co-authoring in M365 is amazing and there is no need to convert in and out of something like BookStack. Use Microsoft solutions for Microsoft products.

https://support.microsoft.com/en-us/office/document-collaboration-and-co-authoring-ee1509b4-1f6e-401e-b04a-782d26f564a4

@A9G-Data-Droid commented on GitHub (Apr 16, 2024): > Quite easy. 3 persons from our service desk would like to add docs or chapters depending our actual requirements. Additionally 5 developer add their parts and would like to enhance existing docs. So, many persons with different knowledge work on the same docs. Impossible for „word“. That’s why we use BookStack. But we will still use our templates from the office app. Not adding a new pdf template to bookstack. Just want to export the content and import it into office or markdown etc. This workflow you are describing is the ideal use case for Editing a shared Word doc in M365. You upload the file to a SharePoint site, which is also the backend for Teams and OneDrive so it works there too. Then you can see everyone editing the document live. It's wild. Co-authoring in M365 is amazing and there is no need to convert in and out of something like BookStack. Use Microsoft solutions for Microsoft products. https://support.microsoft.com/en-us/office/document-collaboration-and-co-authoring-ee1509b4-1f6e-401e-b04a-782d26f564a4

OVERLORD commented

2026-02-04 23:34:00 +03:00

@ssddanbrown commented on GitHub (Sep 7, 2025):

I'm going to go ahead and close this off since desire has been relatively low for the complexity (specifically to support & maintenance) added for supporting such more complex rich text formats.

This is better suited to using external converters as referenced above, to convert the BookStack-native HTML formats to whatever your need.

@ssddanbrown commented on GitHub (Sep 7, 2025): I'm going to go ahead and close this off since desire has been relatively low for the complexity (specifically to support & maintenance) added for supporting such more complex rich text formats. This is better suited to using external converters as referenced above, to convert the BookStack-native HTML formats to whatever your need.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/BookStack#1039