Shapes placed incorrectly after conversion to HTML and PDF


we noticed a few bugs when converting an excel document to pdf or html. Some shapes are placed at a wrong position or rotated.

Here are a few example screenshots (left screenshot always is the excel original, right version the broken one in html/pdf):
Excel to PDF
Arrow is roated:
image.png (36.4 KB)

Excel to HTML
Arrow is aligned incorrect in its cell:
image.png (42.9 KB)
image.png (16.6 KB)

Arrow starts / ends at wrong location / cell (this probably just is the same as before just with the other arrow type looking different):
image.png (74.7 KB)

Arrow also rotated again:
image.png (40.1 KB)

One arrow disappears:
image.png (4.2 KB)

Additionally, the HTML has some cells at the bottom which are not visible in the xlsx (and also not the pdf):
image.png (60.2 KB)

Code for reprodction:

            var lic = new License();

            var wb = new Workbook(@"S:\tmp\in.xlsx");


Test input and output files: (81.5 KB)

Thanks for your support


Thanks for the template file and screenshots.

Please notice, I am able to reproduce the issues you described regarding Excel to HTML (issues seen when opening the output HTML file in Google chrome) and Excel to PDF renderings. The following two tickets are logged for your issues into our database:

  • CELLSNET-48192 - Arrow shapes placed incorrectly after conversion to HTML
  • CELLSNET-48193 - Arrow shapes placed incorrectly after conversion to PDF

We will evaluate your issues thoroughly and try to figure these out soon.

Once we have an update on any of the issues, we will let you know.


I noticed the issues are listed as suspended and wanted to ask if there is any more feedback on it yet.

Additionally I wanted to remark, that with the latest Aspose version there are some imrpovements already: the lower arrows now look correct:
image.png (3.9 KB)

But the bigger, upper one, still is wrongly rotated, so it is is not fully fixed.

Thanks, for your help,


Thanks for your feedback.

We gradually improve rendering shapes and their placements in the output HTML/PDF. The tickets are still suspended. Anyways, we will evaluate it further and get back to you with latest updates.

Your issues(CELLSNET-48192,CELLSNET-48193) have been resolved and the fixed functionality will be released with version 23.6. If you need this feature urgently, you can also consult our hot fix.
Here is the resulting file I generated using the latest function: (74.8 KB)

The issues you have found earlier (filed as CELLSNET-48192,CELLSNET-48193) have been fixed in this update. This message was posted using Bugs notification tool by johnson.shi


thanks for fixing the bugs of the missaligned shapes. However it seems there is a new bug which wasn´t there in the old version, please see the following screenshots with the old (left) and current (right) compared. Some of the cells are missing their background color:
2023-06-12_16-06-45.png (28.9 KB)
2023-06-12_16-07-21.png (102.3 KB)

Only saving as HTML seems to be affected by this.


Thanks for the screenshots and details.

We reproduced the issue as you mentioned by using your template XLSX file. We confirmed the issue (some cells are missing their background colors in XLSX to HTML conversion) as per the screenshots when opening the output HTML into Google chrome.

We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.

Issue ID(s): CELLSNET-53530

You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.

@Serraniel ,

This is to inform you that your issue has been resolved. The fix will be included in an upcoming release (Aspose.Cells v23.7) that we plan to release in the first half of July 2023. You will be notified when the next version is released.
Herer is the result html after fix for your reference: (41.4 KB)

The issues you have found earlier (filed as CELLSNET-53530) have been fixed in this update. This message was posted using Bugs notification tool by johnson.shi