Excel (XLS, XLSX) to HTML Converter

The converter works on one sheet at a time. If the workbook has several tabs, run the conversion once per sheet and combine the results in your page, or link to separate tables.

How to convert a spreadsheet

1. Drag a file onto the dropzone or click to choose one.
2. Wait for the sheet list to populate.
3. Select the sheet you want to export.
4. Leave “First row is header” on if the first row contains column names. Turn it off if the first row is data.
5. Review the preview and the row/column notice.
6. Click Copy HTML, or download the generated .html file.
7. Paste the markup into your page and add CSS for borders, spacing and responsive overflow.

The converter does not upload the file, so a large workbook is limited by your browser's memory rather than by a server upload cap. Very large sheets can still be slow to parse.

The 300-row and 60-column limit

Only the first 300 rows and 60 columns are converted. The header row counts toward the 300. If the sheet is larger, the preview shows a warning and the extra rows or columns are omitted from both the preview and the generated HTML.

This cap keeps the page responsive and prevents a giant table from freezing the browser. For a larger dataset, split the sheet into smaller ranges, export several tables, or use a server-side reporting tool. Do not assume the downloaded HTML contains the whole workbook.

Empty trailing rows collapse, so a sheet with formatting far below the data may still produce a shorter table than expected. Check the preview for the actual row count before publishing.

What is not preserved

HTML tables carry values, not spreadsheet formatting. Fonts, fills, borders, number formats, merged cells, comments, conditional formatting, charts and images are not included. A formula is converted to its displayed value, not to a live calculation.

Dates and numbers may appear differently from Excel because the converter reads the underlying value. A currency cell may lose its symbol, and a date may appear in a different order. Check those columns before publishing, especially for prices, deadlines and statistical tables.

Merged cells are a common source of confusion. The HTML table cannot span cells in the same way unless you add colspan or rowspan manually. If the layout depends on merged headers, expect to edit the markup after conversion.

Where the output works well

• CMS pages: paste a simple data table into a rich-text editor that accepts HTML.
• Documentation: add a comparison or specification table without retyping it.
• Email templates: use inline CSS on the table for better client support.
• Static sites: drop the markup into a page and style it with the site's table classes.
• Prototypes: show realistic tabular data before a backend is ready.
• Accessibility review: add captions, scope attributes and responsive wrappers to the generated table.

For a responsive layout, wrap the table in a container with horizontal scrolling rather than shrinking the font. Wide tables are hard to read on a phone, and a scroll container preserves the column relationships.

Privacy, accuracy and limits

The file is read locally in the browser. The page does not send the workbook to Newisty and does not keep a copy after you close the tab. The copy button uses the clipboard, so the generated markup may remain there until another copy replaces it.

The converter is not a spreadsheet engine. It does not recalculate formulas, resolve external links, preserve macros or validate the data. It also does not sanitise the meaning of the content; it only escapes HTML characters. Review the table for accuracy before publishing.

If the output looks empty, check that the selected sheet actually contains data and that the header setting is appropriate. If only part of the sheet appears, check the 300-by-60 limit. If the table is garbled, confirm the file is a real .xlsx, .xls or .csv rather than a renamed file of another type.

Making the generated table accessible

A bare table is a start, not a finished accessible component. Add a <caption> that describes the table's purpose, and use scope="col" on header cells so assistive technology can associate each column with its data. If the first column is a row label, mark those cells as scope="row" headers. Keep the header option on when the first row contains labels; otherwise the table has no clear structure.

Do not use an empty cell to create visual spacing. Screen readers announce empty cells and the table becomes harder to navigate. Use CSS padding or borders instead. If a cell spans multiple columns, add the correct colspan and test the reading order, because a visual merge is not automatically an accessible one.

For a wide table, wrap it in a container with overflow-x:auto and a keyboard-focusable region. Add a short instruction such as “Scroll horizontally to see all columns” if the table is wider than the screen. On mobile, consider showing fewer columns or splitting the table into two related tables rather than shrinking the text to an unreadable size.

Styling the output

The converter does not add classes or inline styles, so the table inherits your page's defaults. A simple style block can add borders, padding, a header background and zebra striping. Use border-collapse: collapse for a compact grid, and set a minimum width only when you also provide horizontal scrolling.

Keep numeric columns aligned consistently, usually to the right, and text columns to the left. Do not centre every cell; alignment helps readers compare values. If the source has a total row, style it with a heavier top border rather than relying on a background colour that may not print.

Check the table in both light and dark themes if your site supports them. A hard-coded black text colour can disappear against a dark background. Use inherited colours or theme variables, and test the hover and focus states if the table contains links.

Frequently Asked Questions