Google Sheets and Excel Limits Small Businesses Hit (2026)

The documented limits of Google Sheets and Excel that matter to a small business running operations on them: cell and row limits, how many people can edit at once, co-authoring rules, Apps Script quotas and API limits, with the official sources.

Floot ·

Key Takeaways

  • Size caps are generous. Google Sheets allows up to 20 million cells or 100 MB per spreadsheet. Excel allows 1,048,576 rows by 16,384 columns per worksheet. Few small businesses reach them.
  • Concurrent editing is the limit people feel. Google says up to 100 people with view, edit or comment access can work on a file at the same time. Excel co-authoring needs Microsoft 365 and files on OneDrive or SharePoint, and the most recent save wins a conflict.
  • Automation runs on quotas. Apps Script stops a run after 6 minutes and limits triggered runtime and emails per day: 90 minutes and 100 recipients on a free account, 6 hours and 1,500 recipients on Google Workspace.
  • Apps reading your sheet share an API quota. The Google Sheets API allows 300 read and 300 write requests per minute per project, and 60 of each per minute per user.
  • Limits are a symptom. Hitting quotas usually means the sheet has become a database and an automation platform. That is the moment to consider moving that process to an app.

Quick-Start Prioritization Framework

LimitGoogle SheetsExcelWho hits it
SizeUp to 20 million cells or 100 MB per spreadsheet1,048,576 rows × 16,384 columns per worksheetBusinesses logging every transaction for years
Text in one cellCells over 50,000 characters are removed when converting from Excel32,767 characters per cellLong notes pasted into cells
People at onceUp to 100 with view, edit or comment accessCo-authoring via OneDrive or SharePoint with Microsoft 365Busy shared rotas and job lists
Script run time6 minutes per execution (Apps Script)Not covered hereScripts that loop over many rows
Emails from scripts100 recipients a day (free), 1,500 (Workspace)Not covered hereReminder and notification scripts
API requests300 reads and 300 writes a minute per project; 60 per userNot covered hereApps and integrations built on the sheet

Spreadsheets feel limitless until a business starts using them as a shared system: ten staff editing from phones, a script that emails reminders, a form feeding a tab, an app reading the sheet through an API. Then the limits that Google and Microsoft document start to matter. Some are hard caps, like the number of cells. Others are quotas, like how many emails a script can send each day. And some are behaviours, like what happens when two people change the same cell. This guide collects the limits small businesses actually run into, quoted from Google’s and Microsoft’s own documentation as checked on 17 November 2026, and explains what each means in practice and what to do about it.

Google Sheets: size limits

Google’s Drive help page on file limits says spreadsheets created in or converted to Google Sheets can have up to 20 million cells or 100 MB. Cells count across every tab, including empty ones inside the used range, so a wide sheet with many unused columns uses up the allowance faster than you might expect.

What it means in practice

A jobs log with 30 columns could hold over 600,000 rows before reaching 20 million cells. Long before that, though, a sheet with hundreds of thousands of rows and many formulas becomes slow to open on a phone. Performance, not the cap, is what most businesses feel.

Converting from Excel

The same Google page says that when you convert an Excel file, any cell with more than 50,000 characters is removed in Sheets. It matters if you keep long notes or pasted emails in cells.

What to do

Archive old rows into a separate file once a year, delete unused columns and tabs, and avoid whole-column formulas that recalculate over a million empty cells.

Excel: size limits

Microsoft’s Excel specifications page lists a worksheet size of 1,048,576 rows by 16,384 columns, and 32,767 characters per cell. Workbook size is otherwise limited by available memory and system resources.

What it means in practice

The row limit is reachable for businesses that log every sale, scan or sensor reading. For staff rotas and job lists it is not. The practical limit is again speed and file size, especially when the file is synced through OneDrive and opened on phones.

Editing at the same time

This is where shared operational spreadsheets usually feel the strain: several people changing the same file, often the same rows, from different devices.

Google Sheets: up to 100 people at once

Google’s Workspace Learning Center says up to 100 people with view, edit or comment permissions can work on a Google Docs, Sheets or Slides file at the same time. Google’s help also says that above that, only the owner and some editors can edit, and suggests publishing the file as a web page if more people only need to view it.

For a small business, 100 is rarely the issue. The issue is what happens well below it: one person sorts or filters the whole sheet while another is typing, a row is pasted over a filtered range, or two people change the same cell. Sheets keeps version history, but restoring one wrong cell without losing others’ work is fiddly.

Excel: co-authoring rules

Microsoft’s co-authoring article says real-time co-authoring needs a Microsoft 365 subscription and files saved to OneDrive, OneDrive for Business or a SharePoint Online library, in .xlsx, .xlsm or .xlsb format. SharePoint on-premises sites don’t support it. When two people change the same thing, the most recent save wins. If someone opens the file in a version that doesn’t support co-authoring, others can get a “locked” error. Offline edits made through OneDrive sync aren’t merged until the computer is online again.

Excel’s legacy shared workbooks

The older “shared workbook” feature, still listed in Microsoft’s specifications, allows up to 256 users to have a file open at once but can’t be used in a workbook that contains Excel tables. For most teams, co-authoring is the route to use today.

What to do

Give each person their own area to write in (one tab per crew, one row per job they own), protect ranges they shouldn’t touch, and avoid sorting a shared sheet in place: use filter views in Google Sheets so each person sorts only their own view. If many people need to update records all day, a database-backed app is the better structure, because each record is saved on its own.

Apps Script quotas (Google)

Many small businesses automate their Google Sheets with Apps Script: email a reminder when a date is near, copy form responses into a tab, send a daily summary. Google publishes quotas for this, and they differ between free Google accounts and Google Workspace.

QuotaFree (gmail.com) accountGoogle Workspace
Script runtime6 minutes per execution6 minutes per execution
Total runtime of triggered scripts90 minutes a day6 hours a day
Email recipients (MailApp)100 a day1,500 a day
URL Fetch calls20,000 a day100,000 a day
Triggers20 per user per script20 per user per script
Simultaneous executions30 per user30 per user

What it means in practice

A reminder script that emails 40 staff three times a day hits the 100-recipient limit on a free account. A script that loops through 50,000 rows calling the sheet cell by cell can run past 6 minutes and stop halfway, leaving the sheet partly updated. Google says quotas can change without notice.

What to do

Use Google Workspace rather than a personal account for business scripts, read and write ranges in bulk rather than cell by cell, and log what each run did so a half-finished run is visible. If your automations have grown to dozens of triggers, they have become an application; consider building one properly.

Sheets API limits (when apps read your sheet)

Apps built on top of a Google Sheet (including some no-code builders and integrations) read and write it through the Google Sheets API. Google’s usage limits page says there is a read request limit of 300 per minute per project and 60 per minute per user per project, with the same limits for writes.

What it means in practice

For a handful of staff, these limits are invisible. For an integration that syncs often, or a busy morning when everyone opens the app at once, requests can be refused and retried, which shows up as slow loading or stale data. Platforms that use Sheets as a data source usually cache and batch to stay inside the limits, and some publish their own row caps for spreadsheet sources.

Limits of no-code apps built on spreadsheets

If you put an app on top of a spreadsheet, the builder adds its own limits on top of Google’s and Microsoft’s. Two examples from the vendors’ documentation:

  • AppSheet’s help centre says not to exceed 100,000 rows or 1,000 columns in a spreadsheet used by an app, and sets a compressed data size limit of 5 MB or 10 MB (depending on the device) for all the data in one app.
  • Glide’s documentation (for Glide Classic) says rows from spreadsheet data sources have a total cap of 25,000 rows across all tables.

The limits that aren’t in any documentation

Some of the most important limits are about how spreadsheets work rather than numbers on a help page.

Permissions are file-level or range-level

You can share a file and protect ranges, but you can’t easily say “each cleaner sees only their own rows.” Businesses end up keeping a separate cut-down copy for staff.

Validation can be bypassed

Microsoft says Excel’s data validation shows messages and prevents invalid entries only when users type data directly in a cell; when data is copied or filled, the messages do not appear. Our guide to keeping data clean covers this in depth.

There is no status workflow

A spreadsheet can hold a Status column, but it can’t stop someone setting “Paid” before “Invoiced,” or notify the next person when a status changes, without scripts.

When the limits mean it’s time to move

Hitting one of these limits occasionally is a reason to tidy up. Hitting them regularly is a sign the spreadsheet is doing jobs it wasn’t designed for.

  • Scripts regularly fail on runtime or email quotas.
  • People’s edits collide daily and you restore from version history every week.
  • You keep separate copies of the same sheet for different staff because of permissions.
  • An app or integration built on the sheet is slow or shows stale data at busy times.
  • You archive rows monthly just to keep the file usable.

If you move a process to an app

Floot, the AI app builder that publishes this site, builds apps with their own Postgres database, logins and roles, scheduled jobs and email, so reminders and per-person visibility don’t depend on spreadsheet quotas. You can import your existing sheet as a CSV.

Frequently Asked Questions

What is the maximum size of a Google Sheet?

Google says spreadsheets created in or converted to Google Sheets can have up to 20 million cells or 100 MB.

How many rows can Excel handle?

Microsoft lists 1,048,576 rows by 16,384 columns per worksheet, and 32,767 characters per cell.

How many people can edit a Google Sheet at the same time?

Google says up to 100 people with view, edit or comment permissions can work on a Docs, Sheets or Slides file at the same time. Above that, only the owner and some editors can edit.

Why does my Apps Script stop halfway?

Apps Script stops any single execution after 6 minutes. Read and write data in bulk ranges, split work into batches, or move heavy automation into an app with scheduled jobs.

How many emails can a Google Apps Script send a day?

Google’s quotas page lists 100 email recipients a day for consumer (gmail.com) accounts and 1,500 for Google Workspace accounts when using MailApp.

Does Excel let several people edit at once?

Yes, through co-authoring, which needs a Microsoft 365 subscription and the file saved on OneDrive, OneDrive for Business or SharePoint Online in .xlsx, .xlsm or .xlsb format. When two people change the same thing, the most recent save wins.

Sources