In table editor add view modes that make it much easier to navigate big tables that control the column width based on several factors modes: (normal mode is as is) Compact: -makes any row that has nothing in any cell on this page to the shortest width possible based on table header - makes uuid columns show up as xxxxx...xxxxx so you can quickly identify by first and ending numbers but don't need a giant row
Expanded: - makes row expand to fit the longest value up to x characters in that row
and/or make it smart and open in compact mode, but when you click on anything in a specific smartable column it expands to show the full column like uuid or date/time
Also make it usable to move column rows in the viewer only and have it remember those changes and show them as sort does, so if you add a column that way at the right side you can move to the left for easy access or open when comparing 2 columns for issue when in dev mode.
horizontal scrolling is the most painful repetitive action because it is fixed at slow speed on most devices
smartable columns would be uuid, date/time, because you can always make them compact or view short in and change back and forth easily <img width="889" height="441" alt="Screenshot 2026-07-02 at 10 47 00 AM" src="https://github.com/user-attachments/assets/5fbcd7b5-a01a-4cbb-87f4-0e59bc9fabc8" />
The user suggests adding view modes to the Table Editor to improve navigation of large tables. They propose 'Compact' and 'Expanded' modes to adjust column widths dynamically. The user also requests the ability to rearrange columns for easier comparison and reduce horizontal scrolling. A workaround using the SQL Editor is provided by another user.
There isn't an equivalent to this in the Table Editor today beyond manually dragging column widths, so this is a reasonable Feature Request — upvoting the thread helps the Studio team gauge demand.
As a workaround for wrangling big tables in the meantime, the SQL Editor lets you control exactly what you see, e.g. shortening UUIDs so rows stay compact:
select substring(id::text, 1, 6) || '…' as id, name, created_at
from public.your_table
limit 100;