Consider the scenario where "opening the inventory sheet takes forever." Not only inventory, but also customer lists, project status, and billing source data all reside in separate tabs within the exact same spreadsheet.
In situations like this, it is not breaking because it reached the limit. Long before approaching the capacity ceiling, usability reaches its breaking point first.
On September 10, 2026, the Google Sheets cell limit was increased from 10 million to 20 million, entering general availability. Rolling out sequentially starting with Rapid Release domains, Scheduled Release begins on September 28, taking up to approximately 15 days to reflect. This applies not only to new files, but also to existing files and data imported from Excel or CSV.
Doubling the limit is unquestionably a positive update. However, problems resolved by raising the limit and problems that remain are entirely separate.
Performance degrades well before hitting the limit
The cell limit is the line where "exceeding this prevents saving." On the other hand, operational issues begin much sooner.
The trigger for operational friction is rarely the raw cell count itself.
- Volume of formulas. If
VLOOKUPorARRAYFORMULAruns across every row, recalculations trigger with every single cell edit - Concurrent editors. When several people have the same sheet open, one user inserting a row shifts the edit position for another
- External file references. If the destination linked via
IMPORTRANGEis heavy, rendering here is forced to wait - Scope of conditional formatting. Applying rules to entire columns compounds the processing load as rows increase
In other words, just because a sheet can hold up to 20 million cells does not mean it will run smoothly with 10 million cells. The increased limit provides headroom for importing and processing large datasets; it does not mean daily operational ledgers should continue growing indefinitely.
Four symptoms that persist despite expanded limits
Certain operational headaches cannot be solved by reducing cell counts or expanding limits. If you encounter these, the solution is not cleaning up files.
Unable to tell who changed what. While revision history exists, it is not designed to track in business terms why last month's inventory count had a specific value.
Columns you need to hide. When trying to conceal only unit prices or costs, teams end up splitting sheets and linking them with IMPORTRANGE, ultimately obscuring which version is authoritative. Because permissions are fundamentally file-based, they do not align well with column-level requirements.
Inability to prevent input errors. Data validation provides some restrictions, but row insertions or paste actions easily bypass them. Empty cells and full-width spaces end up mixed into aggregations.
Manual repetition of the same tasks every month. Copying the previous month's data at the start of the month, overwriting dates, and repasting totals. This procedure exists solely inside the operator's head.
These requirements are difficult to satisfy merely by adding capacity. Evaluate not by the number of matching symptoms, but by the business impact of accidents and the effectiveness of current safeguards.
Operations suitable for spreadsheets vs. those that are not
The criteria for drawing the line are not data volume, but the following three factors.
First, how many people edit simultaneously. Google Sheets is designed for collaboration, so five concurrent editors is not unexpected. The issue is not just headcount, but the extent to which approvals, locking, and data consistency are required when updating the same records at once.
Second, who the errors reach and how far they travel. If an error is contained entirely within the spreadsheet, whoever notices can fix it. If those numbers flow into invoices or purchase orders, you need safeguards that stop mistakes at the entry stage.
Third, how many years the sheet will be used. For a three-month project, thorough engineering is unnecessary. For a ledger used over five years, structuring it so handoffs succeed across personnel changes is well worth the investment.
If all three criteria land on the heavy side, it is time to evaluate building a dedicated system. If speed is the primary issue, check whether the current sheet can be streamlined before rebuilding: remove whole-column conditional formatting, move unused tabs to separate files, and reduce IMPORTRANGE calls. Such adjustments frequently restore perceived performance.
When migrating, avoid building everything at once
Even when deciding to build a dedicated system, there is no need to construct all functionality immediately. Several phased approaches exist.
- Extract data entry first. Keep reporting and viewing in spreadsheets while building separate input forms with validation. If the goal is stopping entry errors, this step alone delivers results
- Introduce a no-code business app layer. Keep the spreadsheet as the underlying database while creating dedicated interfaces and permission controls. Key evaluation factors are summarized in The scope of building business applications with AppSheet
- Keep everything contained within the spreadsheet. If a single screen suffices, building a mini-app directly on the sheet is an option. What can be addressed in-house is discussed in Mini-apps on spreadsheets and the boundaries of in-house development
If automation is written in Apps Script, processing runtime constraints may be encountered first. Refer to When hitting the 6-minute limit in Apps Script to determine whether splitting tasks or rewriting the system is needed.
What to do next
Open the spreadsheets currently used in your business and document two items: number of concurrent editors and whether numbers from the sheet leave the company.
Even with few users, handling personal data or billing amounts may demand strict controls. Rather than setting an arbitrary headcount threshold, write out the necessary requirements for permissions, input validation, and auditing.
If non-capacity requirements cannot be satisfied, what is needed is defining how many of the rules currently enforced manually inside the sheet should be shifted into software safeguards.
GleamHub provides free IT and Google Workspace consultations covering ledger audits, delineating what can remain in spreadsheets versus what to migrate to systems, and phased migration architecture. Because implementation depends on operational content and team size, please reach out via Contact Us.
Sources
- Doubled cell limits in Google Sheets now generally available — Google Workspace Updates
- Faster performance and doubled cell limits in Google Sheets — Google Workspace Updates
- Google Workspace Weekly Recap - September 4, 2026 — Google Workspace Updates
- Files you can store in Google Drive — Google Docs Editors Help
