Limits
Every number here is a real, enforced ceiling. Most of them you will never meet — they exist to keep pages readable and refreshes fast, not to ration anything. The ones worth planning around are called out as you go.
Notes
| Limit | |
|---|---|
| Note text | 32,000 characters (roughly 5,000 words) |
| Attachments | 10 MB per file, 10 files per note |
| Comment | 4,000 characters |
The note cap is the one you're most likely to hit, and it's deliberate: long notes summarize badly and read badly. Attach the full document and write a summary as the note, or split it into several notes — AI reconnects them when it builds a page. [1] has the reasoning and explains what AI can and can't see inside an attachment.
Pages
| Limit | |
|---|---|
| Title | 1,000 characters |
| Instructions | 32,000 characters |
| Notes matched per refresh | 500 |
| Notes read per refresh | about 320,000 characters of note text, plus AI summaries for about 60,000 more |
| Written per refresh | about 32,000 tokens — roughly 24,000 words |
| Total page content | 128,000 characters |
| Pages per space | about 50 |
| Removed notes remembered per page | 100 |
Notes matched per refresh. Each refresh searches your notes and considers up to 500 of them for this page — the best matches first. This applies to ordinary pages; a page that takes all your notes does no searching and has no such cap (see "How a page picks up notes" in the Pages guide). This is not a cap on how many notes a page can hold, and nothing is thrown away:
- A later refresh picks up where the last one left off. It skips the notes already attached, so the next 500 best candidates get their turn. A page whose subject genuinely covers more than 500 notes fills up over several refreshes rather than all at once.
- Notes you attach yourself — by pinning, by dragging a note onto the page, or through the API — never go through this at all.
Removed notes remembered per page. Removing an unpinned note from a page records it, so the next refresh does not simply put it back. A page remembers the last 100 such removals; past that the oldest is forgotten and that note can be matched again. If you find yourself fighting a page this often, pin the notes you do want instead, or let the page collect everything and curate it by hand.
A page is easier to read below 500 notes, too. If a page is pulling in that many, it is usually trying to cover too much, and the next limit is the one that actually shows: a refresh reads about 320,000 characters of note text in full, so a very large page gets matched in full but reads part of itself in condensed form. Somewhere well under 500 notes, a page stays sharp for AI and for you. Treat the number as a sign to narrow or split, not a ration.
Notes read per refresh. When the notes attached to a page add up to more than AI can read in one pass, pinned notes are read first, then the most recently updated. Notes past that point are included as their short AI summary instead of in full, and only when even that does not fit is a note left out altogether. Either way a line at the top of the page says what happened. Everything else about the page is unaffected — no links are lost, and the notes come back in full if the page later gets smaller.
A note only has a summary once Mikipage has analyzed it, which happens for notes longer than about 200 words. A short note needs no summary: it is already short enough to be read whole.
Written per refresh. A single refresh writes at most ~24,000 words. This is far more than a page anyone reads end to end, and a page that genuinely needs more is a page that wants splitting. If a refresh does run into the ceiling it fails rather than handing back half a document, and the page keeps its previous content until the next successful refresh.
All three are symptoms of the same thing — a page trying to cover too much. Three fixes, in order of how well they work:
- Narrow the page. Tighten the instructions to a specific angle rather than everything.
- Split it. Instead of one "Work Projects" page, make one per project. Notes can feed several pages, so nothing gets duplicated.
- Remove less relevant notes so AI concentrates on what matters.
Pages per space. Beyond roughly 50, a page can fall outside the search AI uses to find candidates, and a legitimately related note may quietly lose its link. Pinned notes are never affected. If you're near the limit, prefer fewer, broader pages — or a separate group.
See [2] for how pages work, and [3] for what a refresh costs.
Groups
A group holds 30 members, counting the owner — so an owner can invite 29 others. There is no limit on how many groups you belong to, or on how many notes and pages a group holds.
History
Notes and pages keep their last 5 versions for 30 days. A version is written when the content itself changes — for a page that means its text, so editing only the title or the instructions doesn't create one.
Very large pages keep fewer than 5. History is capped by total size as well as by count, and when a page's content is long, older versions are dropped early to make room for the newest one. The current version is never affected.
Anything else
The API enforces the same note and page limits as the website: a write over any of them comes
back as 413 content_too_large rather than being quietly trimmed. [4] lists the rest
of the error codes.
Questions about a limit that isn't here? Ask via the chat button, or email support@mikipage.com.
No comments yet.