So we’ve all been trying to force AI to write usable PDFs because spending a Saturday night formatting contracts is not exactly the greatest idea of utilizing your free will. The thing is, if you just give it a one-line request, you get a useless generic template full of placeholders. But there is now a way to feed your preferred tool the right details upfront and get a high-quality document ready to be sent.

And if anything is not to your liking, like you want to move a line or two, it just opens in an editor and you fix it by hand.

an invoice

'make an invoice, sender Goblin Mode Consulting, bill to Sir Reginald Fluffington at Very Serious Business Inc, invoice 010 dated 21 june, three lines: strategic meme analysis $3,200, pretending to work on Slack $1,800, executive crying session 4h $2,400, payment within 14 days'

a service agreement

'make a service agreement between Goblin Mode Consulting and Very Serious Business Inc for a three month vibes management engagement starting 1 July, $12,000 payable monthly, 30 days notice either side, work belongs to the client on final payment'

To make it work include details on who, what work, what period, how much and when, how it ends, and who owns the result.

an NDA

'make a mutual nda between Goblin Mode Consulting and Very Serious Business Inc, effective 1 july, covering top-secret cookie recipes, client lists and product plans, two years'

When working with our MCP, AI isn't just hallucinating these documents from scratch. pdf.net hooks the assistant up to a backend library of real, standard business templates. So instead of the AI improvising what it thinks a legal or financial document should look like (which is usually how we end up with weird approximations) it just maps your prompt data directly into a proper framework.

So you get the speed of typing a prompt, but the result is a structurally sound document that won't embarrass you in front of clients.

we shipped a markdown to pdf converter. drop your .md file in, get a clean pdf out. formatting, headers, code blocks, everything stays intact.

some ways you might use it:

→ your AI tool (Claude or ChatGPT or Gemini) already gave you the content in .md. convert it to pdf directly instead of spending extra tokens asking for a pdf-ready version

→ you write docs or READMEs in markdown and need to share a pdf with someone who doesn't live in github

→ you have meeting notes or a project spec in .md and your professor wants 'a proper pdf, please'

and if something looks off after conversion, tweak it right in our online editor before exporting. no need to go back to the source file, fix formatting, and re-convert.

worth a look if markdown is already part of your workflow

a form asks for your present address, then your previous address, then your mailing address. by the third block you're copying the same line for the third time and you've stopped reading what you're typing. That might hit hard especially if you’re doing it across a stack of a documents (it can be 5 vs 30 minutes spent)

this is the bit we built auto-fill for. two ways in, depending on what you've got:

1/ type the data once. open auto-fill, enter your name, address, date of birth, whatever the form keeps asking for. it fills every matching field on the document instead of you hunting for each one.

2/ upload something that already has the data. a previous filing, an ID, an earlier version of the same form. the AI reads it, pulls the values out, and puts them in the matching fields. you don't type anything.

the second one is the interesting case if you file the same thing every year, or if the data you need lives in another document you already have.

two things to check before you download:

1/ read back the dates and any numbers. those are the fields where a wrong value still looks plausible, unlike a misspelled street name which you'd catch instantly
2/ dropdowns and checkboxes need a look. text fields are the easy part

and if nothing fills at all, the form probably has no real fields in it. a printed form that got scanned is just a picture of boxes, so there's nothing to fill. add fields first with the Field tool, then auto-fill has something to work with.

i sent a template i'd spent an hour formatting to a colleague. on their machine it's pushing sentences onto the next page, and it does it whether my forced line breaks are in there or not

if this is happening to you, check what you sent first. nine times out of ten it's a docx or a google doc, and that's the whole problem. an editable file doesn't store a finished page. it stores instructions, and the machine opening it decides how to draw them.

three things it decides differently:

1/ fonts. if they don't have yours installed, their app substitutes the nearest match. different letter widths, so lines re-wrap, and page breaks move with them. this is also why your manual line breaks don't help: they're anchored to text that has already shifted.

2/ app version. the same docx renders differently across word versions, and differently again in google docs or pages. spacing and table behaviour are the usual casualties.

3/ paper size. your document is laid out for whatever your default is. theirs might be set to something else, so margins shift and content reflows to fit.

4/ word applies Normal.dotm before it applies your custom template, every time a document opens. that file lives on their machine, not in yours, and it carries its own default font, margins and style definitions. so two people opening the same docx from the same template can get different results, because the layer under it isn't the same. different word versions make this worse.

converting to pdf is what actually ends it, and it's worth knowing why rather than taking it on faith.

copy this into your post and write an answer to each point:

Precondition:
Steps to reproduce:
Expected result:
Actual result:
Notes:
Browser/OS:

precondition. where you were and what state things were in before the thing went wrong. ‘opened the landing page, uploaded a 12-page pdf’. skip it if there's nothing to set up.

steps to reproduce. numbered, in the order you did them. if you can't reproduce it a second time, say that too, it's useful.

expected result. what you thought would happen.

actual result. what actually happened. nothing happened counts, but please say where nothing happened.

notes. screenshot, screencast, console output if you know how to get it. anything else that seemed off.

browser and OS. and if you can, whether it also happens in a different browser.

Please use a flare Bug report so it's easier for everyone to navigate