Each Quip folder supports a maximum of 1,000 documents, spreadsheets, and sub-folders. Folders exceeding this limit experience slow loading times, sync issues, and may become unresponsive. If your folder is at or approaching the limit, this article explains how to reorganize existing content and how to use a private-folder-plus-link-sharing architecture with Salesforce automation to avoid the limit entirely for document-heavy use cases.
The simplest approach is to break a large folder into sub-folders. For example, a single "Sales Documents" folder with 1,200 items could be reorganized into sub-folders by year, region, or product line — each staying well under the 1,000 item threshold.
To create a sub-folder, open the parent folder, click the Compose button, and select New Folder. Then move documents into the appropriate sub-folder using drag-and-drop or the Move to option.
For organizations using Quip Document Components on Salesforce records, the recommended architecture avoids Quip folders entirely. Instead:
This approach scales without limits because Private folders are not subject to the 1,000-item cap, and document access is governed by Salesforce record permissions rather than Quip folder membership.
Example: A support operations team uses Quip Document Components on Case records to generate case resolution documents. Instead of adding all documents to a shared Quip folder (which would hit the 1,000-item limit after enough cases), documents are created in the connected user's Private folder with link sharing enabled. Salesforce record access determines who can see each document — no folder management required.
To automate document creation into a private folder with link sharing, use a Salesforce Record-Triggered Flow with the following Quip actions:
See Use Salesforce Flow to Automatically Add a Quip Document to a Folder for a full step-by-step Flow example that can be adapted to this architecture.
000389228

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.