If a doc lives in a workspace that is on a Free Coda plan, it may encounter limits on how many objects it can contain. For more on doc size and how it's calculated, please see this article.

For the Free Coda plan, there is a 50 object limit on free docs. Pages, tables & views, buttons & controls, and formulas all count as objects in a doc. There is also a 1000 row limit for free docs

Additionally, you can add up 1 GB of attachments on top of you doc size.

If you are approaching the limit for number of objects in your doc, there are a few organizational tips and tricks you can use to decrease the number of objects in your doc without changing its contents or utility.

Now that you can collapse and expand text, tables, views and lists within a page, you can create a cleaner looking page that contains a lot more information.

For example, if you have a separate page for each meeting and its notes, consider having just one page for all meeting notes, and a heading for each meeting. If you collapse each heading, doc viewers can come to the meeting notes page, see the list of meeting notes available, and expand only the content they wish to review.

Or perhaps you have one top level page for drafted content, and a separate one with final drafts nested underneath it. Consider moving the earlier draft(s) beneath the final draft on the same page, and collapsing it under a header.

You can see more on collapsible content here.

With pages that nest within each other, the top level page (previously the folder) is an editable object within your doc. If you previously had the first page within a set of pages solely serving as a project overview or a directory of resources or teammates, consider moving that overview content to the top level page's editable area to free up a page.

When you nest pages with several levels of hierarchy, it's a good time to think about your overall doc structure. For example, if you previously had a folder that was a catch-all of supporting details for other pages, consider nesting those supporting pages under the content they're meant to support. A little bit of re-organizing can remove the need for a page that was previously a folder (or two, or three . . .) of appendix material.

Finally, if you've got empty folders, tables that no longer spark joy, or pages are older versions of new-and-improved pages with more current data, consider deleting these older objects. Remember: views, controls and buttons can be deleted to free up space as well.