Live now / How the index works
How the live index works
This site is a read-out. The index it reads is built by CamsFinder, and it is worth knowing what it does and does not do before you trust a number on a page.
CamsFinder builds its live index by reading what the cam platforms publish, giving each performer one profile page and linking out to the room it is broadcast in. A performer enters the live set when the platform reports the room open and leaves when the stream ends, which is why a count is a measurement rather than a published figure. Listings and profiles are rebuilt at most once every 60 seconds; the slowest pages, insights and the FAQ, run on 15 minutes.
An index, not a cam site
CamsFinder runs no cam rooms, hosts no video and stores no imagery of its own. It reads what the platforms already publish and hands the visitor on to the platform the performer broadcasts on. That one fact decides how the counts behave, what a profile is for, and why the per-brand counts never add up to the site total.
CamsFinder is a search engine for cam performers. It runs no cam rooms, hosts no video and stores no imagery of its own. What it does is read what the cam platforms already publish, give each performer a single profile page, and hand the visitor on to the platform the performer actually broadcasts on.
That distinction decides everything else. Because the index does not own the rooms, it cannot decide when one opens. A performer enters the live set when the platform reports the room as open and leaves it when the stream ends. Nothing on the CamsFinder side schedules that, which is why a live count is a measurement rather than a published figure.
It also decides what a profile is for. The profile is the stable part: one address per performer that survives the room closing, collecting the tags, the photos and the videos the platform publishes. The listings are the moving part, and they are rebuilt often enough to keep up.
What the counters on this site measure
Every counter on camsfinder.info asks the same live data service one question: how many rooms match this filter right now. The answer is the total the service reports for that query at that instant.
Three consequences follow, and it is more honest to state them than to round them away. The number changes between two loads of the same page. The per platform counts do not sum to the site wide total, because each filtered question is answered a fraction of a second apart. And a platform reading zero has no open rooms in the feed at that second, which is not the same as a platform being gone.
Nothing here is cached and re-served as if it were fresh. If the feed does not answer, the page says so instead of showing a stale number.
How often each page is rebuilt
CamsFinder rebuilds pages on a cycle rather than caching them for the day, and the cycle is set per page type, shortest where the content moves fastest. Listings, profiles and the home page sit at 60 seconds, tag pages at 10 minutes, reviews and comparisons at 5, insights and the FAQ at 15. The values below were read out of the route files on 2026-09-02.
| Page type | Rebuilt at most once every |
|---|---|
| The home page | 60 seconds |
| Category listings, including brand and attribute pages | 60 seconds |
| Performer profiles, photos and videos | 60 seconds |
| Tag pages | 10 minutes |
| Cam site reviews | 5 minutes |
| Head to head comparisons | 5 minutes |
| Video pages | 5 minutes |
| The country index | 5 minutes |
| Insights articles | 15 minutes |
| The FAQ | 15 minutes |
These are ceilings, not promises of freshness: a page is rebuilt on the next request after its window expires, so a page nobody asks for is not rebuilt at all.
What a URL tells you
CamsFinder addresses are readable on purpose: the first segment is one of the four categories, the second is either a brand or an attribute, and a third segment crosses a brand with an attribute. Attributes come from 6 dimensions holding 36 slugs in total. Every one of those combinations is a real page with its own address rather than a search query.
CamsFinder addresses are readable on purpose. The first segment is one of the four categories. The second is either a brand or an attribute. A third segment crosses a brand with an attribute.
Attributes come from 6 dimensions: ethnicity, age, hair, eyes, body, language. Content tags and the performer's country add two more, and those two are deliberately not multiplied against every brand, because a brand crossed with a rare country is usually an empty page and an empty page is worth nothing to anyone.
Profiles sit under a brand segment of their own, which is where every room card on this site points. Editorial pages, the reviews and the head to head comparisons, sit at the top level next to the categories.
Where the outbound links go
Two kinds of link leave this site. Text links and the cards this page builds go to camsfinder.com, tagged so the traffic can be told apart from anything else. Clicks inside a live widget go to the cam platform through the widget service, which is what makes the widget a widget rather than a screenshot.
Nothing on camsfinder.info hosts a stream, a thumbnail or a photo. The imagery in the widgets and in the cards is served by the platform the performer broadcasts on, straight to your browser.
Reading a zero
Three brands in the feed report no open rooms at various times, and one brand CamsFinder lists reported none at all on the day this site was built. Rather than hide those rows, the platform list keeps them and shows the zero. A list that only shows the winners is not a read-out.
The measurement file
One reading of the feed is published as plain JSON at /data/snapshot.json, so any number quoted from this site can be checked against the moment it was taken. It holds the site-wide total, the four category counts and a count for each of the 13 brands, with the timestamp that makes them mean anything. It carries no performer names, no room ids and no imagery.
Snapshot measured 2026-09-03 at 10:59 UTC: 24,279 open rooms across 13 brands.
Questions about the index
Four questions cover what a reader needs before trusting a number on this site: why a count moves between two loads, who serves the streams, how often a CamsFinder page is rebuilt, and what happens to a performer once the room closes. Each is answered below from the same route files and the same feed behaviour described above.
Why does the live count change between two page loads?
The count is the size of the live set at the moment the page asked, and cam rooms open and close continuously. Two loads a minute apart will not agree, and the per platform counts will not add up to the total, because each filtered question is answered a fraction of a second apart from the others.
Does CamsFinder host the streams?
No. CamsFinder is a directory and aggregation service. The streams and the thumbnails are served by the platform the performer broadcasts on. CamsFinder gives each performer one profile page and links out to the room.
How often is a CamsFinder page rebuilt?
Listings, performer profiles and the home page are rebuilt at most once every 60 seconds. Tag pages run on a 10 minute cycle. Reviews, comparisons, videos and the country index run on 5. Insights and the FAQ run on 15.
What happens to a performer when the room closes?
The profile page stays at the same address. It drops out of the live listings, which is what the counters on this site measure, and comes back when the room reopens.
See it for yourself
The grid below runs against the same feed the numbers above describe, so the two can be compared without leaving the page. It carries its own data and keeps working even when the counters cannot reach the feed. Clicks inside it go to the cam platform; the text links on this site go to camsfinder.com.