VKT Toolkit · August 28, 2026 · 6 min read

How to Copy a Table From a Website to Excel (Without Losing Formatting)

You find the perfect data table on a government portal, a research site, or a company report page. You select it, Ctrl+C, switch to Excel, Ctrl+V — and the result is a mess. Columns shifted, merged cells vanished, numbers stored as text, half the rows collapsed into one.

You're not doing anything wrong. The problem is how browsers copy tables. This guide explains why it breaks and gives you 4 fixes, from quick workarounds to a one-click tool you'll use every day.

Why Web Tables Break When You Copy-Paste Into Excel

When you select a table on a webpage and press Ctrl+C, the browser copies HTML markup, not structured spreadsheet data. Excel then tries to interpret that HTML, and things go sideways:

• Merged cells — HTML uses rowspan and colspan to merge cells. Excel's paste doesn't always reconstruct them, leaving gaps or shifted columns;
• Nested elements — <div>, <span>, <br> inside cells create phantom line breaks or extra columns;
• Whitespace chaos — non-breaking spaces ( ), tabs, and newlines inside cells get pasted as literal characters;
• Numbers as text — formatted numbers like "1,234.56" sometimes arrive as text strings that Excel won't sum or sort correctly;
• Invisible tables — some sites use display: flex or CSS Grid to look like tables but aren't <table> elements at all — copy-paste gives you a wall of text.

The root cause: browsers copy rendering, not structure. You need a tool that reads the underlying HTML table directly.

Fix 1: Paste Special in Excel

A quick partial fix. After copying the table from the browser:

1. In Excel, right-click a cell and choose Paste Special (or Ctrl+Alt+V);
2. Select Unicode Text or Text format;
3. Use Data → Text to Columns to split on tab delimiters.

This preserves more data than a normal paste, but merged cells still break and you'll spend time manually fixing columns. Good for a one-off, painful for daily use.

Fix 2: Google Sheets as Intermediary

Copy the table from the browser, paste into Google Sheets, then download as Excel (.xlsx). Google Sheets handles HTML tables slightly better than Excel's direct paste, and the export is clean. Downside: you need a Google account, the data passes through Google's servers, and merged cells still don't survive perfectly.

Fix 3: Browser DevTools (For Developers)

Open DevTools (F12), find the <table> element in the Elements panel, right-click it, and use a Console script to extract the data as JSON or CSV. This is the most accurate method — but it requires technical knowledge and is impractical for non-developers or for quick daily use.

Fix 4: One Click With VKT TableGrab (The Keeper)

VKT TableGrab reads the HTML <table> structure directly from the page — not the rendered copy — and exports a clean CSV file that opens perfectly in Excel.

What makes it different from copy-paste:

• Merged cells handled properly — parses rowspan and colspan, reconstructs the full grid, repeats values across spanned cells so nothing is lost;
• Auto-detects all tables — no need to manually select; it scans the page and lists every valid table with row × column counts;
• Batch export — export one, selected, or all tables at once;
• UTF-8 BOM encoding — Chinese, Japanese, Korean and other non-ASCII characters display correctly in Excel (no more garbled text);
• Whitespace cleanup — strips extra newlines, spaces, and HTML fragments from cells;
• Privacy-first — all parsing happens locally; table data never leaves your browser.

How to Use It

1. Install from the Chrome Web Store or Edge Add-ons;
2. Visit any page with HTML tables;
3. Click the TableGrab icon — tables are auto-detected and listed;
4. Hover to highlight a table on the page, check to select;
5. Click Export All or Export Selected;
6. CSV downloads instantly — open it in Excel, done.

Comparison: Copy-Paste vs. TableGrab

FAQ

Stop Fighting With Pasted Tables

Two clicks, one clean CSV, zero formatting headaches. Install once, use it on every data page you visit.

More guides in the VKT blog; questions to [email protected].