The numbers on the shared endpoints, and why you will not meet them
A free tool with no account still has to survive the open internet. The limits that do that are published here, because a limit you cannot see feels like a paywall.
— a guard counts requests; a meter counts you.
Every free tool that survives contact with the internet has limits somewhere. The question is what they are protecting. A usage meter protects a price list, counts what you personally have done, and exists to make the paid plan attractive. A saturation guard protects a shared endpoint from a script and forgets you the moment the window closes.
Conxfolio has the second kind, and the numbers are worth printing.
The numbers
Per network address, per five-minute window: twenty document imports, twenty pasted-text imports, sixty ATS checks, forty letter drafts and twelve PDF renders. Claiming a portfolio address is tighter and deliberately so, at ten attempts per fifteen minutes, because that endpoint sends an email.
What normal use looks like against them
Building a résumé involves one import. Tailoring it for a role involves one letter draft and perhaps two checks. A careful afternoon with three applications might spend six checks, three drafts and four PDF exports. Meeting the PDF limit means clicking download once every twenty-five seconds for five minutes without stopping, which is not a workflow.
Why the windows are short
Because a five-minute window recovers on its own. A daily quota punishes a bad afternoon for a whole day and forces the product to know who you are in order to count. A short rolling window needs no identity, resolves itself while you are still reading the page, and does the actual job, which is stopping one script from occupying a shared renderer.
What a saturation guard is protecting
Three of the limited endpoints do real work on a machine somewhere: the parser that sorts an imported document into fields, the scorer, and the PDF renderer, which is a headless browser drawing a page. The renderer is the expensive one, which is why its window is twelve rather than sixty. One script left in a loop against it would make the product slow for everybody, and the guard is the cheapest way to stop that without knowing who anybody is.
The letter engine is limited too, at forty drafts per five minutes, although it costs almost nothing to run: it is deterministic code with no model behind it and no per-request spend, which is the reason a letter draft is free at all. Its limit is there for the same reason a door has a lock rather than because the room is expensive.
What is not limited at all
Everything that happens in your browser. Editing, switching between the 37 designs, previewing, saving versions, and the entire DOCX export, which we measured at zero network requests in your DOCX is built in your browser. Opening a previous ATS report is also free of any limit, because a stored report is not a new request, which is what makes the before-and-after comparison in previous reports cost nothing.
There is also nothing that accumulates. A window is five minutes long and then it is gone, so a heavy afternoon has no effect on the evening, and there is no record anywhere of how much of the product you have used. That is a consequence of having no account rather than a policy applied on top of one, which is the trade set out in why there is no account.
What being refused looks like
The request fails for the rest of the window and works again afterwards. Nothing is deleted, nothing is locked, no counter appears in the interface, and no upgrade is offered, because there is nothing to upgrade to. Every design, both export formats and all four tools are free with nothing held back.
The honest caveat
A limit set per network address is blunt. A large office, a university or a shared connection behind one address can collectively approach a window that none of the people on it would approach alone, and the refusal will look like a fault. Waiting out the window is the whole fix. It is the price of not having an account to attach a quota to, which is a trade explained in why there is no account.
Use it as much as you need
There is no quota attached to you, no counter in the interface and nothing to upgrade. The limits protect the endpoints, not a price list.
Open the résumé builderRead why there is no accountQuestions
- What are the actual limits
- Per address, per five minutes: 20 document imports, 20 pasted-text imports, 60 ATS checks, 40 letter drafts and 12 PDF renders. Claiming a portfolio address is tighter, at 10 attempts per fifteen minutes.
- Do they count against my account
- There is no account. The guard counts requests from a network address over a window and then forgets them. Nothing is stored about who made them.
- Will I hit them while working on a résumé
- It is difficult to. Twelve PDF renders in five minutes is a person clicking download every twenty-five seconds, and sixty ATS checks is one every five.
- What happens if a limit is reached
- The request is refused for the rest of the window and works again afterwards. Nothing is deleted, nothing is locked and no upgrade is offered.
- Do exports have a limit
- The PDF render does, because it runs on a server. The DOCX export does not, because it is built in the browser and never makes a request at all.
Conxfolio is a free set of four career tools: a résumé builder with 37 rendered layouts, an ATS résumé checker that prints its own arithmetic, a cover letter builder that traces every proof paragraph back to the line it came from, and a portfolio builder with 20 authored designs. There is no account to create, nothing is held back for a paid plan, and no language model is used anywhere in the product, so the readers, the score and the letter are deterministic code you can check.