Resume parsing software
Every resume parser turns a CV into fields. What actually separates them is the shape of the deal: what you pay, what you have to agree to before you can start, and how much product you are buying alongside the parse. This is a guide to those three questions, written by one of the vendors in it.
Three kinds of thing get called resume parsing software
They are priced differently, they are bought differently, and most comparison articles mix them into one list where the numbers cannot be compared at all.
Enterprise parsing platforms
A parser plus a skills taxonomy, matching and search, redaction, and connectors into an HR system. Priced by quote or by credit bundle, usually with a sales conversation first. Affinda and RChilli are both in this group.
Self-serve parsing APIs
One endpoint, a published price, a key in minutes. You get the fields and nothing downstream of them. Cheaper per document, and there is no platform underneath — this service is one of these.
Open-source libraries
No licence cost and no vendor. You run it, you tune it, and accuracy on real-world CV layouts is your problem. Genuinely the right answer when you have the engineering time and the volume to justify it.
There is a fourth thing sold under the same words — an ATS with parsing inside it. If you are buying an applicant tracking system, the parser is a feature of it and not a purchase you make separately.
The questions that actually decide it
- Can you find out what it costs? Some vendors publish a figure and some do not, and that difference tells you which sales motion you are entering. A quote form usually means a demo, a discovery call and a procurement cycle before the first parse.
- Are you buying a parse or a platform? A credit that also covers matching, search and a taxonomy is worth more than one that covers a parse. Comparing the two on price per document is only fair when a parse is all you need.
- Does a contract fix where the data goes? A required audit report, a named data region, or a rule that documents may not leave your network — any one of these rules out most of the market before price is discussed at all.
- What is your real volume? Bundles are priced for tens of thousands a month. Most teams evaluating a parser are doing hundreds, and the per-document price at that end of the range differs by more than an order of magnitude between vendors.
- Does it decide anything about the candidate? A parser that scores, ranks or filters is a different regulatory object from one that extracts — see automated employment decision tools.
- Can you test it on your own CVs today? Accuracy claims are all measured by the vendor making them, against their own sample and their own scoring. Ten of your real documents settles more than any published table.
Two named vendors, compared honestly
Both are larger and more capable than this service, and both pages say so before they say anything else.
Affinda alternative →
Audited, self-hostable, regional, fast, and priced by quote. What it does better, and the one thing that is different here.
RChilli alternative →
200+ fields, 40+ languages, a taxonomy and the Oracle and SAP connectors, on a credit bundle from $75. Two published prices, compared.
What this service does not do
Every vendor comparison is written by somebody with an interest in it, this one included. So here is the list of things this service does not do, before the part where it compares favourably at anything. If one of these rows is load-bearing for you, the honest answer is that you want a different vendor and the rest of this page will not change that.
| What | Here | When it decides the question |
|---|---|---|
| Third-party security audit | None. No SOC 2, no ISO 27001, no HIPAA attestation. | If your procurement requires an audit report, this service cannot satisfy it and no amount of description changes that. |
| Data residency | Not offered. There is no EU-only or US-only routing. | If a contract fixes where documents may be processed, buy from someone who offers a region. |
| Self-hosting | No. The parser runs only as a hosted endpoint. | If documents may not leave your network at all, a container you run yourself is the only shape that works. |
| Batch parsing | No. One document per request. | A back-catalogue of 200,000 CVs is 200,000 calls, and a vendor built for bulk will do it in fewer. |
| A contractual SLA | None published. The terms are served as is. | An uptime number you can hold somebody to is a commitment we do not make. |
| Support | An email address. There is no 24×7 desk, no ticketing portal and no account manager. | Enterprise rollouts expect a support organisation, and there is not one here. |
Stated here rather than discovered in procurement. A buyer finds out either way; finding out after an implied yes is the expensive version.
Where this one fits
ResumeJSON is a self-serve parsing API. One endpoint takes a PDF, a DOCX, plain text, or a photo or scan of a CV, and returns typed JSON: name and contact details, every role with dates normalised to YYYY-MM, education, skills, certifications and languages. A field the CV does not state comes back null rather than guessed, and there is no score, rank or fit judgement anywhere in the response because there is no such field in the schema.
Median parse 2.2 seconds, p90 2.4 seconds over 160 parses against the live endpoint. There is no database, and no model endpoint permitted to retain or train on a document may serve a parse.
| Plan | Price | Included | |
|---|---|---|---|
| Basic | $0 | 25 parses a month | A hard cap, so it can never bill you. |
| Pro | $29 | 1,000 parses a month | Overage beyond the quota rather than a blocked integration. |
| Ultra | $99 | 5,000 parses a month | |
| Mega | $299 | 25,000 parses a month |
Metered and billed by RapidAPI. Basic is a hard cap and cannot bill you.