Resume parsing in the browser: PDF and DOCX text extracted on the uploader's device, never on a server
When a resume is uploaded, ofper extracts its text in the uploader's own browser to pre-fill the candidate form. Nothing is parsed or scored on a server, and there is no AI. What it handles, and what it cannot.
Last updated 3 September 2026. Competitor pricing and plan limits are re-verified against each vendor’s own pages.
How it works
When a candidate applies, or a recruiter adds a candidate, the browser opens the file locally with a PDF or DOCX reader, pulls out the text, and fills the form fields it can recognise. The person checks the fields, corrects anything, and submits. The original file is uploaded and kept with the candidate record, de-duplicated by content so the same file is never stored twice.
Why in the browser
Server-side parsing costs compute per resume, and a free product cannot pay per upload. Doing it on the uploader's device makes the cost zero and means the resume text exists on ofper's servers only as whatever the person chose to submit. It is also why there is no server-side fallback: if extraction fails, the form is simply empty.
What it does not do
- No OCR: a scanned or photographed resume produces no text
- No scoring, ranking, keyword matching or AI of any kind
- No parsing of skills, employment history or education into structured fields; the resume is read by a person
- PDF and DOCX only, up to 2 MB
Questions, answered straight
Does ofper read my resume with AI?
No. The text is extracted in your browser to save you retyping your contact details, and the person hiring reads the resume itself. Nothing is scored.
What formats are accepted?
PDF and DOCX, up to 2 MB. Exports from Word, Google Docs and most resume builders work; a scanned image saved as a PDF uploads but yields no text.
Is the resume stored?
Yes, with the candidate record, visible only to the company it was submitted to. Applications to closed jobs fall under ofper's stated twelve-month retention policy.