{"id":16,"date":"2026-05-07T09:51:00","date_gmt":"2026-05-07T09:51:00","guid":{"rendered":"https:\/\/wisegrid.co\/blog\/smartsheet-cell-limit\/"},"modified":"2026-06-10T16:23:20","modified_gmt":"2026-06-10T16:23:20","slug":"smartsheet-cell-limit","status":"publish","type":"post","link":"https:\/\/wisegrid.co\/blog\/smartsheet-cell-limit\/","title":{"rendered":"Smartsheet&#8217;s 500,000-Cell Limit and Error 5636: What&#8217;s Really Going On"},"content":{"rendered":"<p><em>By <a href=\"\/blog\/author\/ryan-kramer\/\">Ryan Kramer<\/a>, founder of Wisegrid. Last updated June 2026.<\/em><\/p>\n<p>You added a few hundred rows, or a form kept filling up, or an automation tried to copy rows into a sheet \u2014 and Smartsheet stopped you with <strong>error 5636: \u201cYou have reached the cell limit of 500,000 cells for this sheet.\u201d<\/strong> Or maybe the sheet didn\u2019t error at all: a form just quietly stopped accepting submissions, and you only found out days later.<\/p>\n<p>This is a troubleshooting guide, written by someone who spent years inside Smartsheet before building an alternative. I\u2019ll explain the symptom, the real cause, the genuine fixes (including the one Smartsheet recommends), and \u2014 honestly \u2014 <strong>when splitting your sheet is actually the right call<\/strong> versus when it\u2019s just trading one problem for a worse one.<\/p>\n<p>Short version up front: a normal <strong>Wisegrid<\/strong> sheet holds <strong>1,000,000 cells with every feature on<\/strong> \u2014 more than 2\u00d7 Smartsheet\u2019s 500K, at the same $9 Pro \/ $19 Business pricing. That\u2019s the answer this whole post keeps circling back to. The Smartsheet fixes below are real, but they\u2019re remediation for a ceiling you don\u2019t have to live with.<\/p>\n<blockquote>\n<p><strong>Key takeaways<\/strong> \u2013 <strong>The cap is 500,000 cells per sheet<\/strong> \u2014 a single number, not a separate row and column limit. It\u2019s <code>rows \u00d7 columns<\/code>, so wide sheets hit it surprisingly early. (<a href=\"https:\/\/developers.smartsheet.com\/api\/smartsheet\/guides\/basics\/limitations\" target=\"_blank\" rel=\"noopener\">Smartsheet API limitations<\/a>) \u2013 <strong>Error 5636<\/strong> is the cell-limit rejection. It can be triggered by a person typing, by a <strong>form<\/strong> adding a row, or by an <strong>automation<\/strong> copying rows. \u2013 <strong>The cruel failure mode:<\/strong> a form on a full sheet can silently stop accepting submissions \u2014 the failure surfaces to the submitter, not to you. \u2013 <strong>Smartsheet does have a ~1,000,000-cell mode<\/strong> (\u201clarge-scale sheets\u201d) \u2014 but it\u2019s <strong>Enterprise-only, admin-opt-in per sheet, and turns OFF Reports, the public API, Search, mobile apps, Proofs, Pivot, form creation, and most automations.<\/strong> (<a href=\"https:\/\/help.smartsheet.com\/articles\/2483463-large-scale-sheets-table-view\" target=\"_blank\" rel=\"noopener\">Smartsheet large-scale sheets doc<\/a>) \u2013 <strong>When splitting is fine:<\/strong> truly archival, cold data you rarely touch. <strong>When it hurts:<\/strong> live data stitched with cross-sheet references and hierarchy rollups \u2014 those have their own tight limits. \u2013 <strong>The shortcut past all of it:<\/strong> Wisegrid\u2019s normal sheet holds <strong>1,000,000 cells with every feature on<\/strong> \u2014 more than 2\u00d7 Smartsheet\u2019s 500K, at the same $9 Pro \/ $19 Business pricing. No special mode, no opt-in, nothing disabled.<\/p>\n<\/blockquote>\n<nav class=\"wg-toc\" aria-label=\"Table of contents\"><div class=\"wg-toc-eyebrow\"><span class=\"lp-dot\" aria-hidden=\"true\"><\/span> On this page<\/div><ul>\n<li><a href=\"#the-symptom-error-5636-and-the-silent-failures\">The symptom: error 5636 and the silent failures<\/a><\/li>\n<li><a href=\"#the-cause-500000-cells-is-rows--columns\">The cause: 500,000 cells is rows \u00d7 columns<\/a><\/li>\n<li><a href=\"#the-cruel-one-a-form-on-a-full-sheet-just-stops\">The cruel one: a form on a full sheet just stops<\/a><\/li>\n<li><a href=\"#fix-1-split-the-sheet-and-when-thats-actually-fine\">Fix 1: split the sheet (and when that\u2019s actually fine)<\/a><\/li>\n<li><a href=\"#fix-2-smartsheets-large-scale-sheets--and-the-feature-desert\">Fix 2: Smartsheet\u2019s large-scale sheets \u2014 and the feature desert<\/a><\/li>\n<li><a href=\"#fix-3-get-a-higher-ceiling-without-the-trade-offs\">Fix 3: get a higher ceiling without the trade-offs<\/a><\/li>\n<li><a href=\"#faq\">FAQ<\/a><\/li>\n<\/ul><\/nav>\n<h2 id=\"the-symptom-error-5636-and-the-silent-failures\">The symptom: error 5636 and the silent failures<\/h2>\n<p>There are three ways you discover the wall:<\/p>\n<ol>\n<li><strong>The explicit error.<\/strong> You (or an API call) try to add rows and get back <code>errorCode 5636: \"You have reached the cell limit of 500,000 cells for this sheet.\"<\/code> This is the clearest signal \u2014 at least you know what happened. <em>(The 500,000-cell cap itself is <a href=\"https:\/\/developers.smartsheet.com\/api\/smartsheet\/guides\/basics\/limitations\" target=\"_blank\" rel=\"noopener\">documented by Smartsheet<\/a>; the exact 5636 text is widely reported in their community forums.)<\/em><\/li>\n<li><strong>The automation that quietly stopped.<\/strong> A workflow that copies completed rows to an archive sheet, or one that generates rows on a schedule, fails when the target sheet is full. The grid looks fine; the automation just didn\u2019t run.<\/li>\n<li><strong>The form that stopped accepting submissions.<\/strong> This is the worst one, and it gets its own section below.<\/li>\n<\/ol>\n<p>If you\u2019re seeing 5636, nothing is broken or corrupted. You\u2019ve hit a hard structural ceiling, and the question is which fix fits your situation.<\/p>\n<h2 id=\"the-cause-500000-cells-is-rows-columns\">The cause: 500,000 cells is rows \u00d7 columns<\/h2>\n<p>Here\u2019s the part that catches people off guard. Smartsheet\u2019s limit is <strong>one number for the whole sheet<\/strong>, not \u201cX rows and Y columns\u201d separately:<\/p>\n<blockquote>\n<p>\u201cA sheet cannot exceed a total of 500,000 cells.\u201d \u2014 <a href=\"https:\/\/developers.smartsheet.com\/api\/smartsheet\/guides\/basics\/limitations\" target=\"_blank\" rel=\"noopener\">Smartsheet API limitations<\/a><\/p>\n<\/blockquote>\n<p>Because the binding constraint is <code>rows \u00d7 columns<\/code>, a <strong>wide<\/strong> sheet runs out of room at a row count that feels absurdly low. Smartsheet\u2019s own documentation spells out the trade-off:<\/p>\n<blockquote>\n<p>\u201cA sheet with 20,000 rows can only have 25 or fewer columns\u201d and \u201ca sheet with 400 columns can only have 1,250 or fewer rows.\u201d \u2014 <a href=\"https:\/\/developers.smartsheet.com\/api\/smartsheet\/guides\/basics\/limitations\" target=\"_blank\" rel=\"noopener\">Smartsheet API limitations<\/a><\/p>\n<\/blockquote>\n<p>So the math that matters for a typical operations or project tracker:<\/p>\n<div class=\"wg-table-wrap\"><table>\n<thead>\n<tr>\n<th>Columns on your sheet<\/th>\n<th>Maximum rows before you hit 500,000 cells<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>10<\/td>\n<td>50,000<\/td>\n<\/tr>\n<tr>\n<td>25<\/td>\n<td>20,000<\/td>\n<\/tr>\n<tr>\n<td>40<\/td>\n<td>12,500<\/td>\n<\/tr>\n<tr>\n<td>100<\/td>\n<td>5,000<\/td>\n<\/tr>\n<tr>\n<td>400<\/td>\n<td>1,250<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/div>\n<p>A 40-column ops tracker \u2014 status, owner, dates, a row of RYG balls, a dozen formula helper columns \u2014 walls out at roughly <strong>12,500 rows<\/strong>. Nobody is sitting there counting cells; the sheet just grows until one day it can\u2019t. <em>(That column-count-driven surprise is my read from years of building on the platform \u2014 the underlying <code>rows \u00d7 columns = 500,000<\/code> math is straight from Smartsheet\u2019s docs above.)<\/em><\/p>\n<p>This is why \u201c500,000 sounds huge\u201d is misleading. The cap is real-world-small the moment your sheet gets wide.<\/p>\n<h2 id=\"the-cruel-one-a-form-on-a-full-sheet-just-stops\">The cruel one: a form on a full sheet just stops<\/h2>\n<p>A Smartsheet form is, mechanically, a row-insert generator pointed at one backing sheet \u2014 <em>\u201cresponses are added as new rows to your underlying sheet\u201d<\/em> (<a href=\"https:\/\/help.smartsheet.com\/articles\/2482754-FAQ-Smartsheet-Forms\" target=\"_blank\" rel=\"noopener\">Smartsheet Forms FAQ<\/a>). That means the form inherits the backing sheet\u2019s 500,000-cell ceiling.<\/p>\n<p>Now connect the two facts: a submission that would push the sheet past 500,000 cells <strong>cannot be written<\/strong>, and the failure surfaces down the form\/submission path \u2014 not as a banner in front of the person who owns the sheet. The result is the failure mode I\u2019ve watched teams discover the hard way: <strong>a public intake form that silently stops collecting responses<\/strong>, found days later when someone asks \u201cwhere did my submissions go?\u201d<\/p>\n<p>It gets worse for high-traffic intake. Smartsheet\u2019s own best-practices guidance for forms admits that big, busy backing sheets slow down:<\/p>\n<blockquote>\n<p>\u201cAs the complexity and size of your sheet increases, you might occasionally experience a delay between when someone submits a form and when you can see their saved responses.\u201d \u2014 <a href=\"https:\/\/help.smartsheet.com\/learning-track\/forms\/best-practices\" target=\"_blank\" rel=\"noopener\">Smartsheet Forms best practices<\/a><\/p>\n<\/blockquote>\n<p>And their recommended remediation is, essentially, to start sharding: <em>\u201ccreating separate sheet copies based on submission categories to distribute the processing load across multiple sheets\u201d<\/em> (<a href=\"https:\/\/help.smartsheet.com\/learning-track\/forms\/best-practices\" target=\"_blank\" rel=\"noopener\">same doc<\/a>). Which leads us to the fixes.<\/p>\n<h2 id=\"fix-1-split-the-sheet-and-when-thats-actually-fine\">Fix 1: split the sheet (and when that\u2019s actually fine)<\/h2>\n<p>Smartsheet\u2019s first-line answer to the cell limit is to <strong>split the sheet<\/strong>: archive old rows to a second sheet, or move columns out to a reference sheet and pull them back with cross-sheet formulas.<\/p>\n<p><strong>When splitting is genuinely the right call \u2014 and I mean this:<\/strong><\/p>\n<ul>\n<li>The data you\u2019d move off is <strong>truly cold<\/strong>. Closed tickets from two years ago, completed projects nobody reports on, raw log rows you keep for compliance but never touch. Archiving cold data into a separate sheet is good hygiene regardless of any cell limit. If that\u2019s your situation, split it and move on \u2014 you don\u2019t need a new tool.<\/li>\n<li>You don\u2019t need formulas, rollups, or hierarchy to reach <em>across<\/em> the split. If the archive is a write-once graveyard, the split costs you nothing.<\/li>\n<\/ul>\n<p><strong>When splitting hurts \u2014 and this is most live operational data:<\/strong><\/p>\n<p>The moment your split data needs to stay connected \u2014 rollups, lookups, a hub sheet summarizing spoke sheets \u2014 you run into the <em>next<\/em> set of limits. Cross-sheet references in Smartsheet are their own rationed resource:<\/p>\n<ul>\n<li>A sheet can have <strong>no more than 100 distinct cross-sheet references<\/strong>. (<a href=\"https:\/\/developers.smartsheet.com\/api\/smartsheet\/guides\/basics\/limitations\" target=\"_blank\" rel=\"noopener\">Smartsheet API limitations<\/a>)<\/li>\n<li>A single reference range caps at <strong>100,000 inbound cells<\/strong>. (<a href=\"https:\/\/developers.smartsheet.com\/api\/smartsheet\/guides\/basics\/limitations\" target=\"_blank\" rel=\"noopener\">same<\/a>)<\/li>\n<li><strong>Hierarchy functions don\u2019t cross sheets at all.<\/strong> <code>CHILDREN<\/code>, <code>PARENT<\/code>, and <code>ANCESTORS<\/code> throw <code>#UNSUPPORTED CROSS-SHEET FORMULA<\/code> when they point at another sheet. (<a href=\"https:\/\/help.smartsheet.com\/articles\/2476176-formula-error-messages\" target=\"_blank\" rel=\"noopener\">Smartsheet formula error messages<\/a>)<\/li>\n<\/ul>\n<p>That last one is the quiet killer. If you split a too-big sheet that uses hierarchy rollups, <strong>the rollups break<\/strong> \u2014 the very structure you split to preserve stops working across the boundary. So \u201csplit the sheet\u201d trades one wall for a more fragile topology with its own ceilings. For a deeper walkthrough of these reference limits and how they bite, see our <a href=\"\/blog\/wisegrid-vs-smartsheet\/\">Wisegrid vs Smartsheet comparison<\/a>.<\/p>\n<p><em>Or skip the split entirely:<\/em> a <a href=\"\/features\">Wisegrid<\/a> sheet holds 1,000,000 cells, so the live data you\u2019d be sharding just stays in one place \u2014 rollups and hierarchy intact.<\/p>\n<h2 id=\"fix-2-smartsheets-large-scale-sheets-and-the-feature-desert\">Fix 2: Smartsheet\u2019s large-scale sheets \u2014 and the feature desert<\/h2>\n<p>Here\u2019s the fix most articles miss entirely. Smartsheet <strong>does<\/strong> offer a path past 500,000 cells. It\u2019s called <strong>large-scale sheets<\/strong> (the \u201ctable\u201d view), and it reaches up to <strong>50,000 rows \/ 400 columns \/ 1,000,000 cells<\/strong>. (<a href=\"https:\/\/help.smartsheet.com\/articles\/2483463-large-scale-sheets-table-view\" target=\"_blank\" rel=\"noopener\">Smartsheet large-scale sheets doc<\/a>)<\/p>\n<p>So why isn\u2019t this the obvious answer? Three reasons, all from Smartsheet\u2019s own documentation:<\/p>\n<ol>\n<li><strong>It\u2019s Enterprise-only.<\/strong> Large-scale sheets are <em>\u201cavailable to Enterprise plans only.\u201d<\/em> (<a href=\"https:\/\/help.smartsheet.com\/articles\/2483463-large-scale-sheets-table-view\" target=\"_blank\" rel=\"noopener\">same doc<\/a>)<\/li>\n<li><strong>It\u2019s admin-opt-in, per sheet.<\/strong> They <em>\u201caren\u2019t automatically activated\u201d<\/em>; you <em>\u201cmust explicitly opt-in each sheet\u201d<\/em> beyond 500,000 cells, and <em>\u201cYou must be an Admin on the sheet.\u201d<\/em> (<a href=\"https:\/\/help.smartsheet.com\/articles\/2483463-large-scale-sheets-table-view\" target=\"_blank\" rel=\"noopener\">same<\/a>)<\/li>\n<li><strong>It turns features off.<\/strong> This is the catch. Smartsheet states plainly: <em>\u201cNot all Smartsheet capabilities are supported at this level of scale at this time.\u201d<\/em><\/li>\n<\/ol>\n<p>What stops working once a sheet goes large-scale (from Smartsheet\u2019s own unsupported list):<\/p>\n<blockquote>\n<p>Reports \u00b7 the public API \u00b7 Search \u00b7 Mobile apps \u00b7 Proofs \/ file reviews \u00b7 Pivot \u00b7 Bridge workflows \u00b7 Salesforce &amp; Jira connectors \u00b7 DataMesh \u00b7 Resource Management \u00b7 Work insights \u00b7 the standard Grid view. \u2014 <a href=\"https:\/\/help.smartsheet.com\/articles\/2483463-large-scale-sheets-table-view\" target=\"_blank\" rel=\"noopener\">Smartsheet large-scale sheets doc<\/a><\/p>\n<\/blockquote>\n<p>On top of that, **form <em>creation<\/em> is disabled<strong> on a large-scale sheet (existing forms can render and submit, but you can\u2019t build or edit one), and <\/strong>automations drop to a thin subset** \u2014 only change-based triggers with a narrow action set (Update Cell, Assign People, Clear Cell, Lock\/Unlock Rows) work; date-triggered, copy-row, and approval workflows aren\u2019t supported. (<a href=\"https:\/\/help.smartsheet.com\/articles\/2483463-large-scale-sheets-table-view\" target=\"_blank\" rel=\"noopener\">same doc<\/a>)<\/p>\n<p>Read that list again. The teams big enough to need a million-cell sheet are exactly the teams that depend on Reports, the API, mobile, and rich automations \u2014 and those are precisely what get switched off to get there. <strong>Smartsheet\u2019s million-cell mode is a feature desert behind an Enterprise paywall.<\/strong> It is technically \u201cpast the limit,\u201d but it\u2019s not a happy place to live.<\/p>\n<p><em>Or skip all this:<\/em> in <a href=\"\/features\">Wisegrid<\/a>, a million-cell sheet <strong>is<\/strong> the normal sheet \u2014 no Enterprise tier, no per-sheet opt-in, and Forms, the API, and rich automations all keep working.<\/p>\n<h2 id=\"fix-3-get-a-higher-ceiling-without-the-trade-offs\">Fix 3: get a higher ceiling without the trade-offs<\/h2>\n<p>The reason the cell limit is so painful isn\u2019t the number \u2014 it\u2019s the <em>consequence model<\/em>. In Smartsheet, growing past 500,000 cells means either sharding your data (and fighting the cross-sheet reference limits) or accepting the large-scale feature desert.<\/p>\n<p>That consequence model is a choice, not a law of physics. I built <a href=\"\/features\">Wisegrid<\/a> so that a <strong>normal sheet holds up to 1,000,000 cells<\/strong> \u2014 and every feature keeps working at that size. No special mode to opt into, no admin toggle, no Enterprise contract, and nothing turned off.<\/p>\n<figure><img decoding=\"async\" src=\"\/blog\/wp-content\/uploads\/2026\/06\/large-sheet-capacity.png\" alt=\"Wisegrid sheet Orders 2025-2026 staying responsive at scale with Forms, Automation, and Live Views available and no features disabled\" loading=\"lazy\"><figcaption>A Wisegrid sheet (\u201cOrders 2025\u20132026\u201d) staying responsive at scale \u2014 a normal sheet with Forms, Automation, and Live Views still available in the toolbar. There\u2019s no \u201clarge-scale mode\u201d to switch on and no features disabled to get here. (This screenshot shows a working sheet at scale; it is not a literal 1,000,000-cell capture.)<\/figcaption><\/figure>\n<p>Concretely, here\u2019s how the two models compare at the wall:<\/p>\n<div class=\"wg-table-wrap\"><table>\n<thead>\n<tr>\n<th>At the limit<\/th>\n<th>Smartsheet<\/th>\n<th class=\"wg-col-win\">Wisegrid<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Normal sheet ceiling<\/td>\n<td>500,000 cells<\/td>\n<td class=\"wg-col-win\"><strong>1,000,000 cells<\/strong><\/td>\n<\/tr>\n<tr>\n<td>Path past it<\/td>\n<td>\u201cLarge-scale sheets\u201d \u2014 Enterprise-only, per-sheet admin opt-in<\/td>\n<td class=\"wg-col-win\">It\u2019s already the normal sheet<\/td>\n<\/tr>\n<tr>\n<td>Reports \/ API \/ Search \/ Mobile past the wall<\/td>\n<td><strong>Disabled<\/strong> in large-scale mode<\/td>\n<td class=\"wg-col-win\">Working (Reports are on our roadmap; the rest work)<\/td>\n<\/tr>\n<tr>\n<td>Build a form on the big sheet<\/td>\n<td><strong>Disabled<\/strong> in large-scale mode<\/td>\n<td class=\"wg-col-win\">Works<\/td>\n<\/tr>\n<tr>\n<td>Automations on the big sheet<\/td>\n<td><strong>Thin subset only<\/strong><\/td>\n<td class=\"wg-col-win\">Works<\/td>\n<\/tr>\n<tr>\n<td>Cross-sheet references per sheet<\/td>\n<td>100 max<\/td>\n<td class=\"wg-col-win\"><strong>200 (Pro) \/ 500 (Business)<\/strong><\/td>\n<\/tr>\n<tr>\n<td>Moving your data over<\/td>\n<td>Manual rebuild<\/td>\n<td class=\"wg-col-win\"><strong>One-click importer<\/strong> (paste an API token, workspace mirrors over)<\/td>\n<\/tr>\n<tr>\n<td>Concurrent edits on a busy sheet<\/td>\n<td>Last-write can clobber<\/td>\n<td class=\"wg-col-win\"><strong>Conflict-safe collaboration<\/strong><\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/div>\n<p>I\u2019ll be honest about what Wisegrid doesn\u2019t have yet, because overclaiming is how you lose people who do real work: <strong>Reports and Dashboards are on our roadmap, not shipped.<\/strong> Native mobile apps and native connectors (Slack, Jira, Salesforce) are roadmap too \u2014 we ship a mobile-tuned web grid and outbound webhooks today. The <code>LET<\/code> and <code>LAMBDA<\/code> formula functions aren\u2019t in yet either. But the modern lookups people actually reach for \u2014 <strong>XLOOKUP, XMATCH, INDEX\/MATCH, FILTER, SORT, UNIQUE, VLOOKUP, HLOOKUP<\/strong> \u2014 are shipped and working, and Forms (with multi-page steps and conditional logic), Gantt with critical path, and Automations are live.<\/p>\n<p>If your live, growing sheet is the problem, the honest move is to stop sharding and get a bigger ceiling that doesn\u2019t take features away to reach it. You can <a href=\"\/signup\">see the grid in your own data<\/a> for free, or paste a Smartsheet API token and watch your workspace mirror over \u2014 formulas translated, hierarchy and attachments intact. For the full step-by-step, see <a href=\"\/blog\/how-to-migrate-off-smartsheet\/\">how to migrate off Smartsheet<\/a>.<\/p>\n<h2 id=\"faq\">FAQ<\/h2>\n<h3 id=\"what-is-the-smartsheet-cell-limit\">What is the Smartsheet cell limit?<\/h3>\n<p>A single Smartsheet sheet <strong>cannot exceed 500,000 cells<\/strong>, where cells = rows \u00d7 columns. There\u2019s no separate row or column hard cap \u2014 the total cell count is the binding constraint. (<a href=\"https:\/\/developers.smartsheet.com\/api\/smartsheet\/guides\/basics\/limitations\" target=\"_blank\" rel=\"noopener\">Smartsheet API limitations<\/a>)<\/p>\n<h3 id=\"what-does-smartsheet-error-5636-mean\">What does Smartsheet error 5636 mean?<\/h3>\n<p>Error 5636 is the cell-limit rejection: <em>\u201cYou have reached the cell limit of 500,000 cells for this sheet.\u201d<\/em> It fires when an action \u2014 a person typing, a form adding a row, or an automation copying rows \u2014 would push the sheet past 500,000 cells. Nothing is corrupted; you\u2019ve hit the structural ceiling.<\/p>\n<h3 id=\"how-many-rows-can-a-smartsheet-sheet-have\">How many rows can a Smartsheet sheet have?<\/h3>\n<p>It depends entirely on how many columns you have, because the limit is on total cells. With 10 columns you can reach ~50,000 rows; with 40 columns only ~12,500; with 400 columns only ~1,250. Smartsheet\u2019s docs give the boundary examples: 20,000 rows max at 25 columns, 1,250 rows max at 400 columns. (<a href=\"https:\/\/developers.smartsheet.com\/api\/smartsheet\/guides\/basics\/limitations\" target=\"_blank\" rel=\"noopener\">Smartsheet API limitations<\/a>)<\/p>\n<h3 id=\"can-i-get-more-than-500000-cells-in-smartsheet\">Can I get more than 500,000 cells in Smartsheet?<\/h3>\n<p>Yes, via \u201clarge-scale sheets,\u201d which reach up to 1,000,000 cells \/ 50,000 rows. But the mode is Enterprise-only, must be opted into per sheet by an admin, and disables Reports, the public API, Search, mobile apps, Proofs, Pivot, and form creation, and limits automations to a thin subset. (<a href=\"https:\/\/help.smartsheet.com\/articles\/2483463-large-scale-sheets-table-view\" target=\"_blank\" rel=\"noopener\">Smartsheet large-scale sheets doc<\/a>)<\/p>\n<h3 id=\"why-did-my-smartsheet-form-stop-accepting-submissions\">Why did my Smartsheet form stop accepting submissions?<\/h3>\n<p>The most common cause is that the form\u2019s backing sheet hit the 500,000-cell limit. A form just adds rows to its backing sheet, so when that sheet is full, new submissions can\u2019t be written \u2014 and the failure surfaces on the submission path rather than as an alert to the sheet owner. Check the backing sheet\u2019s size first.<\/p>\n<h3 id=\"is-splitting-my-smartsheet-sheet-a-bad-idea\">Is splitting my Smartsheet sheet a bad idea?<\/h3>\n<p>Not always. For truly cold, archival data you rarely touch, splitting is good hygiene. It hurts when the split data needs to stay connected: cross-sheet references are capped at 100 per sheet, ranges max at 100,000 inbound cells, and hierarchy functions (<code>CHILDREN<\/code>\/<code>PARENT<\/code>\/<code>ANCESTORS<\/code>) don\u2019t work across sheets at all \u2014 so split-and-stitch breaks your rollups. (<a href=\"https:\/\/developers.smartsheet.com\/api\/smartsheet\/guides\/basics\/limitations\" target=\"_blank\" rel=\"noopener\">reference limits<\/a>; <a href=\"https:\/\/help.smartsheet.com\/articles\/2476176-formula-error-messages\" target=\"_blank\" rel=\"noopener\">formula errors<\/a>)<\/p>\n<h3 id=\"how-is-wisegrids-capacity-different\">How is Wisegrid\u2019s capacity different?<\/h3>\n<p>A normal Wisegrid sheet holds up to 1,000,000 cells with every feature working \u2014 no special mode, no admin opt-in, no Enterprise tier, nothing disabled. Cross-sheet references run 200 (Pro) \/ 500 (Business) per sheet versus Smartsheet\u2019s 100. See the <a href=\"\/features\">Wisegrid features overview<\/a> and the <a href=\"\/blog\/wisegrid-vs-smartsheet\/\">full vs-Smartsheet comparison<\/a>. For the cost side of growing in Smartsheet, see <a href=\"\/blog\/smartsheet-pricing-explained\/\">Smartsheet pricing, explained<\/a>.<\/p>\n<hr>\n<h3 id=\"staring-at-error-5636-right-now\">Staring at error 5636 right now?<\/h3>\n<p>Stop sharding your sheets. See a 1,000,000-cell grid \u2014 with Forms, Gantt, and Automations all still on \u2014 in your own data.<\/p>\n<p><strong><a href=\"\/features\">See the grid \u2192<\/a><\/strong> \u00b7 <a href=\"\/signup\">Start free \u2192<\/a> \u00b7 <a href=\"\/blog\/how-to-migrate-off-smartsheet\/\">Migrate from Smartsheet \u2192<\/a><\/p>\n<hr>\n<blockquote>\n<p><strong>About the author<\/strong> <strong><a href=\"\/blog\/author\/ryan-kramer\/\">Ryan Kramer<\/a><\/strong> is the founder of Wisegrid, a higher-capacity Smartsheet alternative built around a 1,000,000-cell-per-sheet grid, conflict-safe collaboration, and a one-click Smartsheet importer. He built Wisegrid out of first-hand experience hitting the walls in Smartsheet\u2019s grid, pricing model, and capacity limits, and writes about leaving Smartsheet without losing your data. <a href=\"\/blog\/author\/ryan-kramer\/\">More from Ryan \u2192<\/a><\/p>\n<\/blockquote>\n","protected":false},"excerpt":{"rendered":"<p>Hit Smartsheet&#8217;s 500,000-cell limit or error 5636? What&#8217;s really going on, why splitting hurts, when it&#8217;s actually fine, and how to get past the wall.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-16","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/wisegrid.co\/blog\/wp-json\/wp\/v2\/posts\/16","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wisegrid.co\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/wisegrid.co\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/wisegrid.co\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/wisegrid.co\/blog\/wp-json\/wp\/v2\/comments?post=16"}],"version-history":[{"count":3,"href":"https:\/\/wisegrid.co\/blog\/wp-json\/wp\/v2\/posts\/16\/revisions"}],"predecessor-version":[{"id":44,"href":"https:\/\/wisegrid.co\/blog\/wp-json\/wp\/v2\/posts\/16\/revisions\/44"}],"wp:attachment":[{"href":"https:\/\/wisegrid.co\/blog\/wp-json\/wp\/v2\/media?parent=16"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wisegrid.co\/blog\/wp-json\/wp\/v2\/categories?post=16"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wisegrid.co\/blog\/wp-json\/wp\/v2\/tags?post=16"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}