I work on OnePassApps, the team behind app.onepassapps.com. Seven pages on our site are Studio landing pages, one per Studio. Each one lists the tools inside its Studio and then hands you over to them, and this post is about the thing they do NOT tell you: not one of the seven states a single limit of its own. Measured on 12 November 2026 from outside the browser, signed out, with no cookies and no JavaScript.

The handoff, in the page's own words

  • "Processing stays in the current browser tab; export your results before leaving."
  • "Supported formats and device limits are shown by each tool."
  • "No account is required for browser-local processing."
  • "Enable JavaScript to use this Studio."

That is the deal these pages make. They say where the work happens and they say the formats and the limits belong to the individual tools - and then they keep the promise completely. The line is on all seven pages, not one:

  • Processing stays in the current browser tab - on 7 of the 7 Studio pages
  • Supported formats and device limits are shown by each tool - on 7 of the 7 Studio pages
  • No account is required for browser-local processing - on 7 of the 7 Studio pages
  • Enable JavaScript to use this Studio - on 7 of the 7 Studio pages

What the seven pages actually contain

I searched each served page for a limit stated in numbers - a file size, a page count, a file count, a character count - and for the words that usually come with one. Both searches run over the page's visible text, with the script and style blocks removed, so the counts below are what a reader sees and not what the inline code happens to contain:

Studio page Served bytes Limits stated as numbers Cap words
audio 17,114 0 1
colour 17,201 0 1
data 17,367 0 1
files 17,224 0 1
icons 17,286 0 1
image 17,208 0 1
text 17,150 0 1

Across all seven Studio pages that is 0 limits stated as numbers. The one cap word on each page is the 'limits' in the promise line above - seven in total, one per page. The pages name the idea of a limit and then leave the numbers to the tools.

For contrast, the same search over the 22 guide pages found a limit stated in numbers on 11 of 22 of them. The guides are where our numbers live; the Studio landing pages are where you find out which tool to open. We have written the guides' own limit sentences up separately - that write-up is the canonical one: https://dev.to/onepassapps/every-app-page-repeats-its-guides-limits-word-for-word-44-sentences-across-22-routes-7pl

Why that is the right shape, and where it bites

It is a clean split: one page per Studio to choose from, one guide per app for the numbers. The catch is the order of reading. A Studio page cannot tell you that an import is capped or that an export has an output-size limit, because it does not know yet which tool you will open - so if you read the Studio page and then the tool, you have to read the tool's own limits before you commit. The seven Studio pages are not summaries of the tools; they are menus.

We have published the shell of these seven pages before - the tool names and the fact that the pages carry no links are already written up: https://dev.to/onepassapps/seven-studio-shells-49-tool-names-and-zero-links-what-apponepassappscomstudios-sends-before-1plh. This post is about the one thing on those pages that is not a name and not a link: the limits they decline to state.

What I did not do

One host, one day, one network, plain HTTPS, GET only, signed out, no cookies and no JavaScript, so this is a measurement of what the server sent, not of the rendered page, and no tool panel was opened. A limit that only appears after JavaScript runs would not show up here. The byte counts move with the build. The search patterns are mine, not the app's: a page that stated 'under 25 megabytes' in words rather than digits would be counted by my cap-word search but not by my number search, which is why both columns are in the table.

If you want the numbers, the guides are where they are: https://app.onepassapps.com/guides?utm_source=devto&utm_medium=blog&utm_campaign=studio-limits-handoff&utm_content=guides-link

And the Colour Studio is the one to open first: https://app.onepassapps.com/studios/colour?utm_source=devto&utm_medium=blog&utm_campaign=studio-limits-handoff&utm_content=studio-link