Retool New Table Component Auto Column Width Fix

If you've tried migrating from Retool's legacy table to the new table component and noticed that auto column width no longer works, you've hit one of the most commonly reported friction points in the Retool community. Instead of columns spreading evenly across the available viewport, the new table dumps all the extra whitespace into the final column — and if that column happens to be a right-aligned number field, it looks broken. This guide explains why it happens, what your options are today, and how to work around it while Retool's engineering team ships a proper fix.

Why the New Table Component Doesn't Auto-Resize Columns

The legacy table component in Retool was built with automatic column distribution baked in. When your app was set to full viewport width — meaning the max-width of the app frame was set to none — the legacy table would proportionally spread columns across whatever horizontal space was available. Laptop screen or 4K monitor, it just looked right.

The new table component was rebuilt from the ground up with more flexibility and features, but this specific behavior — distributing remaining space evenly across all columns — was not carried over at launch. Instead, the component assigns a fixed pixel width to each column and appends any leftover space to the last column. For most data types that's ugly. For right-justified number columns, it's genuinely confusing to end users who see a huge gap before the value.

Retool has acknowledged this is a bug and an oversight, not intended behavior, and it has been escalated to their internal engineering team.

How This Affects Real Retool Apps

The impact is most visible when:

• Your app's max-width is set to none (full viewport)
• Your users work across different screen sizes — especially large monitors
• Your final column is a number, currency, or other right-aligned type
• You have a small number of columns, making the empty space in the last column more obvious

Several teams have reported holding off on migrating to the new table entirely because of this issue. And that's a reasonable call — if your end users are accustomed to a clean, balanced layout, shipping a regression in visual quality is hard to justify.

Workarounds to Fix Column Width in the New Table Component

Until Retool ships a native auto-resize toggle, here are the practical options available right now:

• Manually set column widths as percentages: In the new table's column settings, you can override the width of each column. Set widths using percentage-based logic by calculating rough proportions (e.g., if you have 4 columns, aim for roughly 25% each). This is tedious but effective for tables with stable schemas.
• Pin the last column width tightly: If the problem is specifically the last column ballooning, manually shrink it to a fixed pixel width that matches its content. This won't make the table fully fluid, but it removes the egregious gap.
• Reorder columns so the last column is text-based: Right-aligned number columns look worst with extra space. If you can place a left-aligned text column last, the excess whitespace is less visually jarring.
• Limit the app's max-width: If your audience is primarily on standard laptop screens, setting a max-width on the app container (e.g., 1440px) reduces the delta between your base layout and the user's screen — shrinking the overflow problem.
• Stay on the legacy table component for now: This is a valid short-term choice. The legacy table isn't going away immediately, and using it while the new component matures is a reasonable trade-off for teams that prioritize visual polish.

What a Good Fix Would Look Like

The Retool community has been clear about what they want, and it's reasonable: a checkbox or toggle at the table level that lets you opt into auto-resize behavior. Something like autoResizeColumns: true as a default-on setting. This would let teams that want fluid, responsive column distribution get it automatically, while teams that prefer fixed column widths (which is valid in many cases, like audit logs or data-dense dashboards) can turn it off explicitly.

Defaulting this behavior to on for new tables is important. The worst outcome is a fix that ships as an opt-in setting that nobody discovers — meaning every team that migrates still hits the same broken-looking layout until they stumble across the toggle in the docs.

Should You Migrate to the New Table Component Now?

If column layout polish is critical for your users, it's reasonable to wait. But if you're building net-new apps or the data in your table is dense enough that the column width issue is minor, the new table component offers genuine improvements: better filtering, server-side pagination, row selection handling, and a more composable column configuration model. The trade-off is real, but for internal tools where users are forgiving and admins control the environment, migrating now and manually tuning column widths is a workable path.

Keep an eye on Retool's changelog and the original community thread for updates. When the fix ships, the community thread will likely be updated first.

Summary

• The new table component does not auto-distribute column widths — all extra space goes to the last column
• This is a known issue acknowledged by Retool's team and flagged for an engineering fix
• Workarounds include manual column width overrides, reordering columns, and capping app max-width
• The community is asking for a default-on autoResize toggle — a sensible ask that Retool should ship enabled by default
• For polish-sensitive apps, staying on the legacy table temporarily is a valid choice