The debate over whether a CV should be a PDF or a web page treats them as competitors. In practice, they solve different problems, and the strongest candidates use both — generated from the same underlying content, so neither one goes stale on its own.
Applicant tracking systems still frequently expect a file upload. Some interviewers print a CV before a panel interview. A PDF is also the format people default to when they want something they can save, forward, or read offline — it's self-contained, and it looks the same everywhere it opens.
A web CV can hold more than a page allows: real portfolio pieces, embedded video, a live GitHub repo list, a contact form that doesn't expose your personal email in plain text. It updates instantly — no re-exporting and re-sending a new file every time you add a role. And it's the only format that can show visit analytics back to you, so you actually know whether anyone's looking.
Most people who maintain both end up with two documents that quietly drift apart — a job added to the web version that never makes it into the PDF, or the reverse. Six months later neither one is fully accurate, and you don't notice until an interviewer asks about something that isn't on the copy they read.
The reliable version of this setup is a single CV that generates both formats from the same content — edit once, and your public page and your downloadable PDF update together. That's the whole reason myCv treats the PDF export as a one-click output of your live page rather than a separate document to maintain: whichever format someone asks for, it's never out of date.
Don't pick one. Keep one source of truth, and let it produce whichever format the moment calls for.
Ready to build yours?
Join for free