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

Free Support Forum - aspose.com

Styles not shown after converting pdf to word

Hi there,

I tried to convert my pdf to word using Aspose.pdf. After the conversion, I couldn’t see any styles (h1, h2, h3) in the resultant document.

Please let me know how to achieve that capability in my out put file.

Attached here is my resultant and my original file for your reference as how it looks like.

Hi Bhim,

Thanks for using our API’s.

I have seen the resultant Installation_Guide_SC80-A4.doc file and as per my observations, I can see Heading text with formatting as displayed in input PDF file. However I have observed that its being treated as Normal text. can you please confirm that you are facing same issue or you have any other observations. Please share the details so that we can further look into this matter.

PS, please take a look over attached Image file which indicates my observations.

Thanks for your reply.

I think you got my point exactly right. It looks like it has got all the headings and sub-headings but are treated as normal text. So, my requirement is to get all those headings and subheading perfectly.

Here is the code I am using to get the resultant output.

// Path of input PDF document
String filePath = @“E:\documentation\Installation_Guide_SC80-A4.pdf”;
// Instantiate the Document object

Aspose.Pdf.Document document = new Aspose.Pdf.Document(filePath);
// Create DocSaveOptions object
DocSaveOptions saveOptions = new DocSaveOptions();
// Set the recognition mode as Flow
saveOptions.Mode = DocSaveOptions.RecognitionMode.Flow;
// Set the Horizontal proximity as 2.5
saveOptions.RelativeHorizontalProximity = 2.5f;
// Enable the value to recognize bullets during conversion process
saveOptions.RecognizeBullets = true;
// Save the resultant DOC file

document.Save(@“E:\documentation\Installation_Guide_SC80-A4.doc”, saveOptions);


Hi Bhim,

Thanks for your feedback. We have logged a ticket PDFNEWNET-39118 in our issue tracking system to investigate the heading styles issue in PDF to DOC conversion. We will keep you updated about the issue resolution progress within this forum thread.

We are sorry for the inconvenience caused.

Best Regards,

Hi there,

I cannot wait for a month for this issue. I am actually unable to use aspose.pdf at all due to this and couple of issues earlier. So, could you please put this issue in a out most priority so that I can get some value of my investment?


Hi Bhim,

Thanks for your inquiry. As we have recently noticed the issue, it is still pending for investigation in the queue. Currently product team is busy to resolve other issues, reported earlier. We will notify you as soon as we made some significant progress towards issue resolution.

Moreover in reference to escalation, we schedule issue investigation and resolution on first come first serve basis. We feel this is the fairest and most appropriate way to satisfy the needs of the majority of our customers. However, if you have subscribed to our priority support service. Then you can escalate the issue using it, as paid support has different queue.

We are sorry for the inconvenience caused.

Best Regards,


well I’ll keep my eye on this issue.

In the mean time, I just wanted to know that is it possible to implement style to existing word document that doesn’t have any styles (take attached doc) using aspose.word? If is possible, please send me the code <span style=“font-size:11.0pt;line-height:107%;
mso-bidi-font-family:“Times New Roman”;mso-bidi-theme-font:minor-bidi;

In the mean time, I just wanted to know that is it possible to implement style to existing word document that doesn't have any styles (take attached doc) using aspose.word? If is possible, please send me the code Snippet.
Hi Bhim,

Thanks for the acknowledgement.

As your query is related to Aspose.Words, so I am moving it to respective forum and my fellow workers from respective team will further look into this matter and will reply accordingly.

Hi Bhim,

Regarding your query related to Aspose.Words, please use the following example code to create and use a paragraph style with list formatting:

Document doc = new Document();

DocumentBuilder builder = new DocumentBuilder(doc);

// Create a paragraph style and specify some formatting for it.

Style style = doc.Styles.Add(StyleType.Paragraph, "MyStyle1");

style.Font.Size = 24;

style.Font.Name = "Verdana";

style.ParagraphFormat.SpaceAfter = 12;

// Create a list and make sure the paragraphs that use this style will use this list.

style.ListFormat.List = doc.Lists.Add(ListTemplate.BulletDefault);

style.ListFormat.ListLevelNumber = 0;

// Apply the paragraph style to the current paragraph in the document and add some text.

builder.ParagraphFormat.Style = style;

builder.Writeln("Hello World: MyStyle1, bulleted.");

// Change to a paragraph style that has no list formatting.

builder.ParagraphFormat.Style = doc.Styles["Normal"];

builder.Writeln("Hello World: Normal.");

doc.Save(MyDir + @“15.7.0.docx”);

I hope, this helps.

Best regards,

Hi there,

Is there any update regarding the issue?

Is there any update regarding the issue?
Hi Bhim,

Thanks for your patience.

As we recently have been able to notice this issue, so its still pending for review. The team has been busy fixing previously reported issues and once we have some definite progress towards its resolution, we will let you know.

Hi there,

It’s been more than couple of month I am waiting for your response regarding the issue and not sure when I can it done. It is ridiculously frustrating. Can’t Imagine how you guys can stay idle after selling product that isn’t mature enough.


Hi Bhim,

Thanks for your patience and sorry for the inconvenience which you have been facing.

As shared earlier, the issues are resolved in first come first serve basis as we believe its the fairest policy to all the customers. Therefore the team has been busy fixing other previously reported priority issues and the problems reported in this thread are pending for review. However I have shared your concerns with product team and have raised the priority of these issues.

As soon as we have some further updates, we will let you know.