[GH-ISSUE #23092] feat: Enable proper table copying to Excel/Google Sheets #58550

New Issue

GiteaMirror · 2026-05-05T23:24:02-05:00

GiteaMirror commented

2026-05-05 23:24:02 -05:00

Originally created by @kai-huracan-tech on GitHub (Mar 26, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/23092

Check Existing Issues

I have searched for all existing open AND closed issues and discussions for similar requests. I have found none that is comparable to my request.

Verify Feature Scope

I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions.

Problem Description

Issue #10126 is related but addresses rich text formatting for regular text, not table structure preservation, pasting it with ctrl+shift+v doesnt solve it.

When copying tables from chat responses using the copy button, the content is copied as raw markdown formatting. When pasting into Excel or Google Sheets, all the content ends up in a single cell instead of maintaining the table structure across multiple cells.

Current behavior:

Click the copy table button on a RAG response table
Paste into Excel/Google Sheets
Result: Raw markdown (e.g., | Column 1 | Column 2 |) appears in a single cell

This is especially problematic when working with large datasets (hundreds or thousands of rows) that need to be analyzed in spreadsheet applications.

Desired Solution you'd like

Modify the table copy button to copy data in a format that spreadsheet applications can parse correctly, but that might then bring other problems.

Use tab-separated values (TSV) format for the clipboard instead of markdown
Or use HTML table format that Excel/Sheets recognize natively

This would allow users to directly paste tables into Excel/Sheets with the structure preserved (data distributed across appropriate cells and rows).

Alternatives Considered

Current workarounds that work but are not ideal:

Manual mouse selection: Selecting the entire table with mouse and copying preserves structure, but this is impractical for large tables and doesn't work well with pagination.

CSV download method (multi-step process):

Click "Download as CSV" button
Open new Excel file
Go to Data tab → Get Data → From File → From CSV
Select the downloaded file and confirm import steps

While functional, this adds 4-5 extra steps compared to a simple copy-paste workflow.

Additional Context

Originally created by @kai-huracan-tech on GitHub (Mar 26, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/23092 ### Check Existing Issues - [x] I have searched for all existing **open AND closed** issues and discussions for similar requests. I have found none that is comparable to my request. ### Verify Feature Scope - [x] I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions. ### Problem Description Issue #10126 is related but addresses rich text formatting for regular text, not table structure preservation, pasting it with ctrl+shift+v doesnt solve it. When copying tables from chat responses using the copy button, the content is copied as raw markdown formatting. When pasting into Excel or Google Sheets, all the content ends up in a single cell instead of maintaining the table structure across multiple cells. Current behavior: Click the copy table button on a RAG response table Paste into Excel/Google Sheets Result: Raw markdown (e.g., | Column 1 | Column 2 |) appears in a single cell This is especially problematic when working with large datasets (hundreds or thousands of rows) that need to be analyzed in spreadsheet applications. ### Desired Solution you'd like Modify the table copy button to copy data in a format that spreadsheet applications can parse correctly, but that might then bring other problems. Use tab-separated values (TSV) format for the clipboard instead of markdown Or use HTML table format that Excel/Sheets recognize natively This would allow users to directly paste tables into Excel/Sheets with the structure preserved (data distributed across appropriate cells and rows). ### Alternatives Considered Current workarounds that work but are not ideal: Manual mouse selection: Selecting the entire table with mouse and copying preserves structure, but this is impractical for large tables and doesn't work well with pagination. CSV download method (multi-step process): 1. Click "Download as CSV" button 2. Open new Excel file 3. Go to Data tab → Get Data → From File → From CSV 4. Select the downloaded file and confirm import steps While functional, this adds 4-5 extra steps compared to a simple copy-paste workflow. ### Additional Context <img width="324" height="218" alt="Image" src="https://github.com/user-attachments/assets/a7f86332-f35c-4086-a635-94ed250d0a5a" />

GiteaMirror closed this issue

2026-05-05 23:24:04 -05:00

GiteaMirror commented

2026-05-05 23:24:05 -05:00

@pr-validator-bot commented on GitHub (Mar 26, 2026):

⚠️ Invalid Issue Title

Hey @kai-huracan-tech, please provide a descriptive title for your issue. Titles that are empty, very short (under 10 characters), or generic (like "issue:" or "feat:") make it difficult for volunteer contributors to understand and triage issues.

Please update the title to reflect the content of your issue.

⚠️ Missing Issue Title Prefix

@kai-huracan-tech, your issue title is missing a prefix (e.g., bug:, feat:, docs:).

Please update your issue title to include one of the following prefixes:

bug: Bug report or error you've encountered
feat: Feature request or enhancement suggestion
docs: Documentation issue or improvement request
question: Question about usage or functionality
help: Request for help or support

Example: bug: Login fails when using special characters in password

@pr-validator-bot commented on GitHub (Mar 26, 2026): # ⚠️ Invalid Issue Title Hey @kai-huracan-tech, please provide a descriptive title for your issue. Titles that are empty, very short (under 10 characters), or generic (like "issue:" or "feat:") make it difficult for volunteer contributors to understand and triage issues. Please update the title to reflect the content of your issue. --- # ⚠️ Missing Issue Title Prefix @kai-huracan-tech, your issue title is missing a prefix (e.g., `bug:`, `feat:`, `docs:`). Please update your issue title to include one of the following prefixes: - **bug**: Bug report or error you've encountered - **feat**: Feature request or enhancement suggestion - **docs**: Documentation issue or improvement request - **question**: Question about usage or functionality - **help**: Request for help or support Example: `bug: Login fails when using special characters in password`

GiteaMirror commented

2026-05-05 23:24:08 -05:00

@tjbck commented on GitHub (Mar 26, 2026):

You can click on copy button to copy with html.

@tjbck commented on GitHub (Mar 26, 2026): You can click on copy button to copy with html.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/open-webui#58550