I work on OnePassApps, so this is our own site, and every figure below was measured from outside the browser with plain HTTPS requests on 7 November 2026. No session, no cookies, no JavaScript.
Our sitemap lists 56 URLs: 22 app routes, 22 guide routes, 7 Studio routes and five others (the home page, the vote board, the plans page, the guides index and the terms page). The seven Studio routes are the odd ones out, because they are the only part of that list a crawler cannot walk through.
What the server actually sends
Each Studio route is a static document. Measured from outside the browser, the seven run from 17,261 bytes (Audio Studio) to 17,514 bytes (Data Studio) - 121,579 bytes for all seven together.
Each one carries a single h1 (Image Studio - OnePassApps), a meta description, one h2 reading What you can do, and one <ul> of tool names. That is the whole page.
The names in that list are plain <li> text. On all seven shells, not one of the 49 names is wrapped in an <a> element.
The one studio link on the page points back at the page
Each shell ends with a single paragraph link - Open Image Studio, Open Audio Studio, Open File Studio, Open Text Studio, Open Data Studio, Open Icon Studio, Open Colour Studio - and on every one of the seven the href is the shell's own absolute URL. The "open" link on a Studio is a link to the page you are already on.
The rest of the links on the shell are the site footer: All apps, Terms of use, Privacy, Refunds and cancellation, Plans and pricing, Support, App guides. Not one of the 49 tool names is among them, and not one of them points at another Studio.
The same list, twice, and it matches
Each shell repeats its tool list in the JSON-LD WebApplication node, as featureList. After decoding the HTML entities and the JSON escapes, the visible list and the featureList are identical on all seven pages.
The escaping is not the same on both sides, which matters if you parse it. On the Text Studio the visible HTML carries Find & replace while the JSON-LD carries Find \u0026 replace; on the Colour Studio the visible HTML carries Picker & converter while the JSON-LD carries Picker \u0026 converter. Both pairs decode to the same two names, so a parser that compares raw bytes sees a difference that is not there.
All seven shells carry exactly the same seven JSON-LD types - BreadcrumbList, ContactPoint, ListItem, Organization, WebApplication, WebPage, WebSite - and all seven declare applicationSubCategory as Browser-local Studio and browserRequirements as Requires a modern web browser.
There is no FAQPage node on any of the seven shells, and there is no question anywhere on them. The visible page says why the page is so thin: Enable JavaScript to use this Studio. No account is required for browser-local processing. The workspace itself is a client-side app, and the shell carries the crash fallback for when that app does not load - OnePassApps stopped working in this tab - as an inert template that /shell-fallback.js only clones into the page when the bundle fails.
The counts
Forty-nine tool entries across the seven shells, and 47 distinct names:
- Data Studio - 11: CSV viewer, Sort / filter, Columns, Remove duplicates, Merge CSV, Split CSV, CSV to JSON, JSON formatter, JSON validator, JSON to CSV, JSON and YAML
- Text Studio - 8: Clean, Case, Duplicate lines, Sort lines, Find & replace, Diff, Markdown, Base64
- Icon Studio - 8: SVG to PNG, PNG to ICO, Favicon pack, App icons, Resize set, Optimize SVG, Recolour SVG, Trim / padding
- Image Studio - 7: Convert, Compress, Resize, Crop, Remove background, Remove metadata, Images to PDF
- File Studio - 7: ZIP files, Unzip files, Batch rename, File hash, Find duplicates, Split file, Join parts
- Audio Studio - 4: Convert, Compress, Trim, Extract
- Colour Studio - 4: Picker & converter, Contrast & gradient, Palettes, Image sampler
Two names appear twice: Convert and Compress, once in the Image Studio and once in the Audio Studio. The other 45 names appear once.
I published the same list of names once before, in a post about the registry inside our JavaScript bundle. This post is about the other half of the story - what the server sends to a crawler, and why none of those 49 names can be followed: the earlier post on the studio registry.
No tool has an address
If the tool names are the only route into the tools, there is nowhere for a link to point. I probed eight of them as URLs and all eight answered 404:
/studios/image/convert, /studios/image/compress, /studios/data/csv-viewer, /studios/data/csv-to-json, /studios/icons/favicon-pack, /studios/text/clean, /studios/colour/palettes, /studios/files/zip-files
A control probe, /studios/doesnotexist, also answers 404, so that is the server answering a path that does not exist rather than a route that is blocked. The bare /studios/ redirects to /studios/image.
There are no guide pages for the studios either. The sitemap's 22 guide URLs carry the same 22 slugs as the 22 app URLs, one for one, and none of them belongs to a Studio.
Who links to a Studio
This is the part that surprised me. I fetched all 56 sitemap URLs and counted the references to a Studio route in each:
- 48 of the 56 pages contain no
/studios/reference at all - the home page is the only page that links all seven, under its
Browser-local Studiosheading, and its JSON-LD lists the same seven - 0 of the 22 guide pages mention a Studio, and 0 of the 22 app pages mention a Studio
- each of the seven shells references only itself
Our llms.txt names all seven as well - it is 17,956 bytes and contains seven /studios/ references - but a crawler following links from a guide or an app page never reaches a Studio, because nothing on those pages points at one.
What I did not do
One build, one fetch per URL, plain HTTPS, no browser and no session, on 7 November 2026. The byte counts are a snapshot of that build. I probed eight of the 49 tool names as URLs and did not try the other 41, so the honest claim is that those eight have no address, not that none of them has one. I did not open a Studio workspace in a browser, so I make no claim about what a tool does once the client-side app has loaded - only about what the server sends before it does.
If you want to try the Data Studio yourself, it is the one with the longest list: the Data Studio. Every app has a written guide as well: the app guides.
I work on OnePassApps, the team behind app.onepassapps.com, and every string quoted in this post came out of a fetch of our own pages on the date above.
Top comments (0)