Convert XLS to HTML Online

Why an Old Excel Sheet Is Not Already a Web Table

XLS is Microsoft Excel’s legacy binary workbook format for Excel 97 through Excel 2003. Its BIFF8 records sit in a Compound File Binary container, not in an HTML document. It can hold worksheets, formulas, charts, cell formats, names, external links, print settings, and other Excel-only information. A single legacy worksheet has at most 65,536 rows and 256 columns, ending at IV. HTML was made for browser documents. Its basic table vocabulary is rows, cells, headings, links, and style rules; it does not have Excel’s recalculation model.

That difference explains why an XLS-to-HTML result should be judged as a published view, not as a new editable master. HTML is useful when a reader needs a searchable table in a browser without installing Excel. The source should remain available wherever calculations, multiple sheets, or the audit trail matter. A page can look close to the spreadsheet while silently becoming static, so the purpose of the output needs to be decided first.

The Export Changes Cell Data Into Markup, Styles, and Linked Assets

Excel can save a workbook, a worksheet, a range, a chart, a PivotTable report, a print area, or an AutoFilter range as a web page. Microsoft’s web-page documentation is unusually specific about this choice: it is not necessary to publish an entire workbook. During export, cell positions generally become <tr> and <td> markup, while colors, borders, widths, and fonts are represented with CSS or old Excel-generated HTML. A formula’s displayed result may appear in the browser, but the formula does not execute in the HTML table.

Images and other objects create another physical change. Microsoft says Excel creates a supporting folder named after the HTML page, such as Page1_files, for graphics and related page assets. Moving only the .html file can therefore leave broken image links. This is a practical reason a web export looks correct on the computer that created it but loses charts or pictures after being uploaded or emailed. Keep the HTML file and its support folder together, or use an export method that embeds assets when the destination allows it.

Benefits of Browser Delivery and the Workbook Details It Leaves Behind

• Gain browser access: a reader can view a table without Excel or a spreadsheet app.
• Gain page linking: HTML can link cells or headings to other web resources.
• Gain selective publishing: Excel can export a range, chart, or chosen sheet instead of the whole workbook.
• Lose calculation: formulas become displayed output, not editable dependencies.
• Lose workbook navigation: hidden sheets, names, and Excel controls do not become normal web-page features.
• Risk detached assets: charts and images may rely on the generated supporting folder.

There is one little-known date trap. Microsoft warns that web pages do not support Excel’s 1904 date system; dates are converted to the 1900 system and can differ by about four years. This affects a workbook originally set to the 1904 system, historically common in some Mac-created files. Test a known date in the browser rather than assuming every displayed cell has the same underlying date meaning.

Browser and Spreadsheet Support Are Not the Same Promise

Any modern browser can render ordinary HTML tables, but that says nothing about opening an Excel-generated web page back in a spreadsheet program. Excel can edit HTML files directly, yet HTML is still not a full fidelity workbook exchange format. Modern Excel opens legacy XLS for compatibility, and LibreOffice Calc can open XLS, but the browser-facing version should be tested in the actual browser and hosting path that readers will use. A desktop preview may load local support files that a web server has not received.

For an accessible public table, use real table headings and a caption or nearby explanation instead of relying on a colored first row. An exported sheet may carry visual styling but not meaningful header markup. Check on a narrow screen too: a 256-column legacy sheet can technically be represented in HTML, but it will be nearly unusable without a scrolling container or a smaller published range.

Failures That Show Up After an XLS Table Goes Online

A common report is “the web page has blank chart boxes.” The cause is usually the missing filename_files folder, not corrupted XLS data. Upload the folder alongside the page and preserve the relative folder name, or regenerate the page with a different asset strategy. Another problem is a table that looks correct but has stale totals. HTML cannot refresh an Excel formula; recalculate and verify the source before export, then identify the page as a dated snapshot when values change over time.

A third problem is shifted dates. Check whether the source workbook uses the 1904 date system, compare a known date after export, and correct the source or the published value before release. Lastly, do not rename an XLS file to .html. Browsers will see binary content, not a table. A converter must read the worksheet and write actual markup.

A Publishing Comparison for Legacy Excel Data

Answers Before You Publish an XLS Worksheet as HTML

Can every sheet appear on one page?
Excel can save a whole workbook with sheet navigation, but publishing selected ranges is often clearer and smaller.

Will users be able to change formulas?
No. HTML presents values and markup; it does not run Excel formulas.

Why are pictures missing after upload?
Copy the generated supporting folder with the page, keeping its relative path intact.

Can a web page preserve a 1904-system date exactly?
Check it carefully. Microsoft documents a conversion to the 1900 date system that can create an approximately four-year difference.

Should the XLS source be deleted?
No. Retain it as the editable record and publish HTML as a tested snapshot.