Nothing to preview yet.
Write the content in Markdown and let the layout be someone else's problem. A Markdown resume converted to PDF keeps a real text layer — which is exactly what an applicant tracking system needs in order to read it.
A résumé is mostly a short list of headings, dates and bullets, and almost all the time spent on one in a word processor goes into fighting the layout rather than improving the content. In Markdown the structure is unambiguous, the file is small enough to keep in version control, and tailoring it for a specific role is a text edit rather than a formatting exercise.
Most large employers parse your PDF before a person sees it, and most parsing failures come down to the file not containing readable text in a sensible order. A few choices matter more than the rest.
The style panel is the fastest way to gain or lose a page without cutting content you wanted to keep. Reduce the margins, drop the body size by a point, and choose a more compact typeface — Inter and Source Serif set tighter than Merriweather at the same size. Turn page numbers off, since a one-page résumé does not need one, and leave the title page off so your name stays at the top of the first page.
Name as the top-level heading, contact details on the line beneath, then one second-level heading per section — Experience, Education, Skills. Under each role, a third-level heading with the job title and dates, then bullets for what you actually did. Nothing more elaborate is needed, and anything more elaborate is where parsers start guessing.
Because the source is plain text, keeping a general-purpose résumé alongside a handful of role-tailored versions is a matter of editing a bullet list rather than fighting a template. The pattern that works: keep one canonical Markdown file under version control, and for a specific application duplicate it, reorder or trim the experience bullets to lead with what that role cares about, and reconvert. The difference between versions is then just text — easy to review, and easy to put back if a tailored cut removed something worth keeping.
A PDF produced by a real browser engine embeds its fonts rather than naming them, so the document looks identical on the reviewer's machine regardless of what is installed there — no fallback face substituting for the one you chose. The tagged output structure matters specifically for a résumé: some applicant tracking systems and accessibility-conscious reviewers read through text extraction rather than visually, and a tagged PDF preserves the reading order — heading, then role, then bullets — in a way a flattened image of a résumé cannot.
A few ideas travel badly regardless of the tool, all for the same underlying reason: a parser has to guess a linear reading order, and these make the guess hard.
Yes, provided the PDF contains real text rather than an image. This converter produces embedded, selectable text with a sensible reading order, which is what parsers need.
Narrow the margins, drop the body size a point, and pick a more compact typeface in the style panel. The preview shows the page count as you change them, so you can stop as soon as it fits.
Yes, if you write them as Markdown links. They stay live in the PDF, so a reviewer can follow them straight from the file.
Markdown has no layout for a headshot the way a visual template does. It can be added as an ordinary Markdown image, but most ATS-focused advice is to leave photos off: they add file weight without helping a text-based parse.
Yes — nothing in the converter enforces a single page. The one-page guideline is a résumé-writing convention rather than a technical limit, and a decade or more of relevant roles is a reasonable case for two.
Every heading becomes a PDF bookmark automatically, with nothing to switch on, so a reader's sidebar will show your section structure. The separate Contents option adds a visible table of contents onto the page, which a one-page résumé rarely wants.
No — start with your name. A hiring manager and an ATS both know what kind of document they are looking at from context, so a label at the top spends space a one-page format cannot spare.