# This doc is too big to sync **URL:** \ **Category:** Ask the Community\ **Created:** [December 18, 2019, 10:35pm UTC](https://connect.superhuman.com/t/this-doc-is-too-big-to-sync/12848 "2019-12-18T22:35:27Z")\ **Posts on this page:** 1\ **Showing post:** 7
**Author:** ![Paul\_Danyliuk](https://yyz1.discourse-cdn.com/coda1/user_avatar/connect.superhuman.com/paul_danyliuk/32/27228_2.png) [@Paul\_Danyliuk](https://connect.superhuman.com/u/Paul_Danyliuk)\ **Post date:** [March 25, 2020, 1:04pm UTC](https://connect.superhuman.com/t/this-doc-is-too-big-to-sync/12848/7 "2020-03-25T13:04:32Z")
Here are a few very short facts. I’ll expand on these in my blog when I have more time. 1. The doc size limit is 125 megabytes. This is 0.json (schema file) and 1.json (data file) size combined in their _uncompressed_ form: 2. The biggest impact comes from button columns and conditional formats. Coda stores buttons very inefficiently: a button is set up on column level and the configuration is the same for all rows, yet in 1.json it’s duplicated for every row. Conditional format settings are also duplicated for each row, regardless if those settings apply for this row or not. They also appear duplicated multiple times per row. Cutting down on buttons and conditional formatting are the most effective first-aid measures to bring doc size down. There are workarounds for buttons that I’ll expand on later. 3. Cross-doc data takes more space than local tables. This is mostly due to table/row identifiers taking not 10 but 64 characters. So every time you reference anything from a cross-doc table, you’re getting formulas that take ~5–7 times more space. Bad news is that Coda stores doc data very inefficiently, as I learned from debugging the 0.json and 1.json files myself. Good news is that there’s room for eventual improvement. --- _[View the full topic](https://connect.superhuman.com/t/this-doc-is-too-big-to-sync/12848)._