A table on a web page you need to actually work with — sort it, total it, filter it. Upload your .html or .htm file above and the tables inside it become a real .xlsx spreadsheet with values in cells.
Below: how to get the page saved in a form that converts cleanly, why some pages come out empty, and the checks to run before you calculate with anything.
Most people arrive here with a web page rather than a file, and how you save it decides everything.
In your browser, use Save Page As and choose the option described as complete or single file rather than HTML-only. Then upload the saved file.
If the result is empty, the page probably builds its content with JavaScript. A great many modern sites send an almost blank HTML shell and fill it in after loading, so a saved copy contains the layout and none of the data. Two ways round it:
<table> element, and copy its outer HTML into a text file. That captures what is actually on screen rather than what the server sent.Many sites also offer a CSV or Excel download somewhere on the page. Worth a look before doing any of this.
Conversion looks for real <table> markup — rows, cells, and ideally a header row in a <thead>. When a page uses that properly, the result is clean.
Three things reliably cause trouble:
Tables that are not tables. Plenty of sites lay out tabular-looking data with styled <div> elements using CSS grid or flexbox. It looks like a table and contains no table markup at all, so there is nothing for a converter to find. Copying the rendered content and pasting into Excel is the practical route.
Merged cells. A header spanning three columns, or a label spanning several rows, uses colspan and rowspan. These translate into merged cells in Excel, which look right and break sorting and filtering. Unmerge them and repeat the values before you try to work with the data.
Nested tables. Older sites, and most email templates, use tables for page layout with the real content in a table inside a table inside a table. Results are unpredictable, and extracting the innermost table by hand is usually faster than fighting it.
This is the step to do before anything else, because getting it wrong produces wrong totals with no error message.
Values from a web page frequently arrive in Excel as text that looks numeric. When that happens SUM ignores them, sorting puts 100 before 20, and everything downstream is quietly incorrect.
The check takes two seconds: select a column of figures and look at the status bar at the bottom of Excel. If it shows a Sum, the cells are numeric. If it shows only Count, they are text.
Common causes on web data:
$1,234.56 often imports as text.12.5% may arrive as a string rather than 0.125.Data → Text to Columns → Finish converts a whole column in one step once you have cleaned the characters out.
Worth a moment's thought, since this tool is often used on someone else's content.
Data displayed publicly is not automatically free to reuse. Many sites publish terms restricting automated extraction or commercial use, and databases carry their own protections in some jurisdictions — the European Union in particular has a specific database right separate from copyright.
In practice: taking a table for your own analysis is one thing; republishing it, or building a product on someone else's data, is another. If a site offers an API or a published dataset, that is the route they have sanctioned and it will usually be cleaner data anyway.
<div> elements rather than real table markup, so there is nothing for a converter to find. Copying the rendered content and pasting into Excel is the practical alternative.Going the other way, Excel to HTML turns a sheet into web table markup. PDF to Excel rebuilds tables from a PDF, Excel to CSV gives plain data for another system, and HTML to Word handles pages that are mostly prose. Browse all Excel tools.