A Google Slides table should show the information an audience needs for the current point, not every row available in a source dataset. Technical support for a large table does not make that table readable during a talk. Treat scope reduction as an editorial decision rather than a formatting failure.
Identify the required comparison
Write the question the table should answer. Select the columns, rows, units, and date range needed for that question. Preserve important exceptions and qualifiers; removing them merely to create a cleaner slide can misrepresent the data.
Build a focused display
Use a native Slides table for the selected comparison and include a clear heading row. Google’s accessibility guidance recommends tables for data rather than using them solely as a page-layout device. Keep labels understandable without requiring the audience to remember an explanation from several slides earlier.
Adjust column widths and row sizes where useful, but do not keep shrinking text to force a full spreadsheet onto the canvas. A concise summary and a separate detailed resource can serve different audience needs.
Verify accuracy and readability
Check every displayed value against the source and explain any rounding or exclusions. Present the slide at the intended viewing size. If viewers cannot identify headings and compare entries comfortably, simplify further or split the material. Review the smaller printed handout separately when one is planned. A readable table should communicate the intended evidence clearly while remaining honest about the larger dataset it summarizes and the limits of the comparison.
References
Reviewed against the linked official product guidance on November 3, 2026. Features, limits, screen labels, and access can vary by account, platform, region, and organization policy.