We're sorry Aspose doesn't work properply without JavaScript enabled.

Free Support Forum - aspose.com

Converting Word to PDF results in indent problem

– Actual Situation –

We trying to convert a Word document, which contains a Image, into a PDF. Those Image is located in the ‘media’ folder of the word document with suffix ‘.tmp’

(e.g. rename word document to ‘word.zip’ and browse to the media folder. In our case there is a image like "…/media/image.tmp)

– Using Aspose Word Converter –

When converting a word document (.docx) into PDF, the included image doesn’t show up at the right position.

– Using Word build-in converter –

The images are at the correct position

– Conclusion –

It seems that Aspose does not handle this image correctly out of the box. Is there any solution for this case?


Thanks for your inquiry.

While using the latest version of Aspose.Words i.e. 16.6.0, we managed to reproduce this issue on our end. We have logged this issue in our bug tracking system. The ID of this issue is WORDSNET-13891. Your request has also been linked to the appropriate issue and you will be notified as soon as it is resolved. Sorry for the inconvenience.

Best regards,


It is to update you that our product team has completed the analysis of this issue and the root cause has been identified. However, because of complexity, the implementation of the fix of this issue has been postponed.

The image is inline and positioned inside a text box which is nested inside a cell. The text box is horizontally positioned relative to the column at 55 pt but MS Word ignores this and puts it on the left side of the cell. Aspose.Words however currently moves it to the right according to position, hence the difference.

As s workaround you can set text box horizontal position to 0. We need to investigate why MS Word ignores the attribute here.

We will inform you via this thread as soon as this issue is resolved. We apologize for your inconvenience.

Best regards,

The issues you have found earlier (filed as WORDSNET-13891) have been fixed in this update. This message was posted using BugNotificationTool from Downloads module by mudassir.raza