Convert XLSX to XLS Online (Excel 97-2003 Format)

From XML Package to BIFF8 Record Stream

An XLSX workbook and an XLS workbook can show the same cells on screen, but they are not two names for the same storage method. Microsoft identifies XLSX as the default XML-based workbook format used by Excel 2007 and Excel 2010 onward, while XLS is the Excel 97-2003 binary file format known as BIFF8. SpreadsheetML places a modern workbook and its worksheets in a package of related XML parts. BIFF8 instead stores workbook information as an older binary record stream designed around the features and grid size of Excel 97 through Excel 2003. Converting XLSX to XLS means translating the parts of the modern workbook that BIFF8 can describe, then dropping, changing, or flattening the parts it cannot. It is a compatibility copy for a specific recipient or legacy system, not a better general-purpose replacement for the original XLSX.

The extension alone matters because old software may recognize BIFF8 but have no reader for the Office Open XML package. Microsoft documented the Office Compatibility Pack as a way for older Office installations to work with the 2007 Word, Excel, and PowerPoint formats, but that is an extra component and not a promise about every old system. Saving an actual XLS copy removes that dependency when the receiving application is built for Excel 97-2003 files. It also moves the workbook into Excel’s Compatibility Mode when a current Excel edition opens the XLS file. That mode is useful because it keeps the legacy format while editing, but it is also a reminder that newer Excel features are being constrained on purpose. Keep the XLSX version as the full-featured master before making any compatibility copy.

The Exact Spreadsheet Limits That Move When You Save XLS

The most important XLS conversion fact is numeric and non-negotiable. Microsoft states that Excel 97-2003 supports 65,536 rows and 256 columns per worksheet, whereas modern XLSX sheets support 1,048,576 rows and 16,384 columns. Data beyond row 65,536 or column IV is not saved in the older format. This can create a second problem when a formula inside the surviving area points to cells outside that boundary: Microsoft says those references return #REF! after the XLS save. Do not rely on a quick visual inspection of the top-left corner; count the source rows and columns, then check the final row and final used column in the saved XLS file. A sheet that fits in rows but uses a lookup table beyond column IV is still too large for a faithful conversion.

Formula arrays bring their own legacy limits. Microsoft’s formula Compatibility Checker says that arrays with more than 256 columns or 65,536 rows are not saved in earlier formats and may produce different results. It also says that Excel 97-2003 supports no more than 65,472 workbook arrays referring to other worksheets; extra arrays are converted to #VALUE! errors. These details explain why a workbook can appear to have a modest amount of visible data yet still fail after conversion: its calculations may use large ranges or many cross-sheet array formulas. The safe response is to run the Compatibility Checker, use its Find link to locate the affected cells, and reduce or restructure the calculation before sharing the XLS copy. A conversion cannot preserve an array shape that BIFF8 does not have room to store.

Five Reasons an XLS Copy Can Help and Hurt

• Help — it targets BIFF8 readers: XLS is the Excel 97-2003 binary format, useful where a recipient or system cannot read an XML-based XLSX package.
• Hurt — the grid shrinks sharply: XLS permits 65,536 rows by 256 columns, rather than the 1,048,576 by 16,384 limits of a modern XLSX sheet.
• Hurt — out-of-range formulas break: references to cells beyond the XLS boundary become #REF!, even when the formula cell itself remains inside the old grid.
• Hurt — multi-table analysis is removed: Microsoft says Data Model features, including multi-table PivotTables, connections, tables, slicers, Power View, and cube functions, are not saved in Excel 97-2003 format.
• Help — Compatibility Mode exposes the choice: current Excel opens the resulting XLS in Compatibility Mode, which helps avoid accidentally adding a feature that the intended older format cannot keep.

Which Versions and Systems Actually Need XLS

XLS is specifically the workbook format for Excel 97 through Excel 2003, not a generic “old Excel” label. Excel 2007 and later use XLSX as their default XML-based format, and Microsoft 365, Excel 2024, Excel 2021, Excel 2019, and Excel 2016 can all open XLS files. Current Excel automatically opens an Excel 97-2003 workbook in Compatibility Mode, according to Microsoft’s file-format guidance. That makes XLS a reasonable delivery option only when the recipient has stated a need for it, such as a legacy import utility or an Excel 2003-era installation. If the recipient uses a recent Excel version, XLSX avoids avoidable limits and retains the wider feature set. Sending XLS “just in case” can be a worse compatibility decision because it deliberately throws away modern capability.

Compatibility is about the application that must use the file, not merely the age of a computer. A newer Windows computer can still host a business application whose importer accepts only BIFF8 XLS, while an old desktop may have the Compatibility Pack installed and open some XLSX files. Ask which program and version is receiving the workbook, whether it needs formulas or only values, and whether it uses more than 256 columns before converting. Microsoft recommends saving a file to Excel 97-2003 Workbook format and reviewing the Compatibility Checker report; its Find link takes the reviewer directly to each issue. That documented workflow is far more reliable than converting and assuming that an old extension means universal compatibility.

Compatibility Warnings That Point to Real Data Loss

The Compatibility Checker is useful only when its warnings lead to a specific correction. Microsoft says its Significant loss of functionality list should be resolved before saving because it can prevent permanent data loss or incorrect results. For a grid-limit warning, use Find, move the excess rows or columns onto another worksheet, and then update formulas to point to the new location if the older recipient can use several sheets. For a large-array warning, reduce the range, break the calculation into smaller blocks, or provide a values-only report if the recipient does not need live formulas. For structured references, Microsoft notes that Excel 97-2003 does not support the feature and converts them to ordinary cell references. Recheck the converted formulas after any change because the visible results can be correct before a later edit exposes a changed reference.

Modern data tools fail for a different reason: Excel 97-2003 has no Data Model or Get & Transform Data capability. Microsoft says Power Query-imported data cannot be refreshed in earlier Excel versions, and multi-table data features are removed from the XLS format. The practical fix is to refresh the query in the modern XLSX first, copy its required output to an ordinary worksheet table, and then send that static table in the XLS copy. This preserves a usable snapshot without pretending that an Excel 2003 installation can refresh a query it does not understand. Keep the XLSX workbook for the owner of the data connection, because the old file is an export result rather than a maintainable query model.

Modern Workbook and Excel 97-2003 File Compared

Questions to Resolve Before Sending an XLS Copy

Will an XLS copy keep every row in my XLSX file?
Only when each sheet fits within 65,536 rows and 256 columns. Microsoft says data outside those limits is not saved, and formulas referring to it can return #REF!.

Why did a table formula change into normal cell references?
Excel 97-2003 does not support structured references. Microsoft says the Compatibility Checker converts them to cell references, so test the formula after conversion and keep the XLSX version for modern table behavior.

Can an Excel 2003 user refresh my Power Query data?
No. Microsoft says earlier versions lack Get & Transform Data capabilities. Refresh the query in the XLSX source, then share a static output table in XLS when a legacy user only needs the results.

What should I do with a Compatibility Checker warning?
Do not dismiss a Significant loss of functionality warning. Use its Find link, correct the named range, feature, or formula, save a new XLS copy, and verify that copy in the intended receiving program.