This issue impacts our organization as well. Splitting to multiple pages is not really the best workaround and exporting PDF is also not a solution either in our use case.

It's been almost 9 long yrs since this bug was reported. I do not understand how it has not been fixed yet!! 

This really impacted our organization , we don't like to use severals pages , and we want export to word not pdf .

It also Affects to version 6.0.1.

Has any progress been made on this bug? It looks unassigned. How long will this status remain?

This has severely impacted our organization, as we have selected Confluence as the leading-edge single-source of record for our documentation. 

The Export to Word function is single-page, so we found this workaround on Stack Overflow:

1. Create a new wiki page
2. Use the {include} macro to pull content in from several pages one at a time
3. Tools > Export to Word

http://stackoverflow.com/questions/26226570/confluence-multiple-page-export-to-word

Unfortunately, there is a limit to how many images will be generated before errors occur, so this requires:

1. Create a large page and then go into the Word doc and replace all of the non-generated images with the images.
2. Create a number of small Includes docs based on where it looks like the big doc failed.
   • This requires an extra effort, as you create one small doc, generate it, and then discover that it throws an error at a certain point
   • So then you create another smaller doc based off of that error point, and then find the new error
   • You repeat the steps until you have a series of small docs with no errors
3. Then you have to combine those docs into a single doc and format that single doc

While all of us who have voted on this feature are aware that there is an Export to Word plugin, it is frustrating to see that there is a perfectly good Export to Word function in Confluence, but there is no way to Export a Tree and we depend on two layers of workarounds just to get it to work properly.

The Export to Word function makes better business sense (in either wiki or documentation mode, depending on the user) if it works properly for exporting pages with many images AND you can export a page tree.

Reopening this because it has had a fair amount of customer interaction since it was closed. This will allow voting and watching etc on the ticket, so we can better assess the impact.

Please vote on and watch the ticket if you are affected by this issue, and you will be notified of any updates. It still may not be high enough priority to make it onto the backlog, but this will allow us to better categorise it.

We are using Confluence for documentation as well and exporting to word is necessary for some users. This is an unfortunate limitation of the application.

Well, same here for us. Also our company (working in the engineering area on a global level) uses confluence for documentation. Sometimes a PDF export isn't the final solution since for exports for some special customers/projects a minor post processing of the content is necessary - and this is done within Word.
Now the workaround using two pages instead of one is indeed a feasible solution - BUT: you aren't always counting the images, are you?

When exporting a page to word images don't display after 50. This is a major problem for our company as we (like most others looking for the same solution) are documenting software and rely heavily on the use of screenshots and images. This was raised originally in 2013 but has been closed as of yesterday. Please re-look at this issue.
Regards,

Issue re-raised by nikki1: CONF-38997