Home/Any AI assistant's Markdown to PDF or HTML
From an AI assistant
Any AI assistant's Markdown to a styled page
Copilot, Perplexity, DeepSeek, Grok, Mistral and the other assistants all answer in Markdown. Once you have that text, the same three steps style and export it.
The source stops mattering once it is Markdown
Every assistant above writes its answers as Markdown text: headings marked with #, tables built from pipe characters, lists, bold text, and code fenced between triple backticks. Paste that text into the editor and it renders the same way no matter which assistant produced it. The three steps are always paste, pick a theme, export.
Confirm the answer is actually Markdown
Most assistants answer in Markdown by default, and their copy control gives you that source text rather than a rendered version. A quick look at the pasted text tells you which you got.
- Headings start with one or more
# characters, not a large bold line. - Table rows use pipe characters between columns, with a dashed line under the header row.
- Code sits between triple backticks, sometimes with a language name after the first set.
If none of that appears and the text looks like formatted rich text instead, ask the assistant to answer in Markdown. That gives you a source file this editor can style, rather than a screenshot-shaped block of text with no structure to render.
What else renders
Past the headings, tables and code that mark Markdown, the editor renders nested and task lists, block quotes, links, images and footnotes, in whatever mix an assistant chose. A pros-and-cons table sits next to a numbered list of next steps in the worked example below, both rendered from the same pasted source without extra formatting work.
Worked example
An assistant's answer to a pros-and-cons question: a two-column table, two headed sections, a numbered list and a closing recommendation, rendered in the Minimal theme.
Here is a summary you can share with the team before Thursday's meeting.
# Four-Day Work Week: Pros and Cons for a 20-Person Agency
A 20-person creative agency asked whether moving from a five-day, 40-hour week to a
four-day, 32-hour week would hold up against client deadlines and billable targets.
The short answer: it can, with two conditions attached.
| Pros | Cons |
| --- | --- |
| Recruiting edge in a market where competitors still run five days | Client meetings compress into four days and can clash |
| Long weekends reduce Friday's usual drop in response quality | Payroll and software costs stay fixed while scheduled hours drop |
| Meetings get trimmed by design, protecting focus time the other four days | Urgent client fixes need a dedicated on-call rotation |
| Easy to reverse in a single department if the trial does not hold up | Some clients may read a shorter week as reduced availability |
## What Changes Operationally
Internal meetings currently run 6 hours a week per person, leaving 34 billable hours
out of the 40-hour week. Across 20 staff, that is 680 billable hours a week. A
four-day, 32-hour week with meetings trimmed to 4 hours a week would leave 28 billable
hours per person, or 560 across the team. Closing that 120-hour gap needs either a
small rate increase on new work or tighter scope on existing retainer hours.
## Client-Facing Considerations
Twelve of the agency's 31 active clients are on retainers with same-day response
clauses. Those twelve need a short amendment covering Fridays and a rotation of two
people a week to handle anything urgent. The other 19 clients are project-based with
no same-day clause, so their contracts need no change for the trial to start.
**Steps to trial it**
1. Pick one department of 6 to 8 people to run the four-day week for one full quarter.
2. Set an on-call rotation so two people cover Fridays for that department only.
3. Send the retainer amendment to the 12 affected clients two weeks before the trial starts.
4. Track billable hours, response time and sick days weekly against the prior quarter.
5. Review the results at week 12 and decide whether to extend the trial agency-wide.
**Recommendation**
Run the trial in one department first rather than switching the whole agency at once.
A 20-person agency has less room to absorb a weak quarter than a larger firm. A
single-department trial keeps the downside contained, and it still produces three
months of real data on billable hours and client response time.
Here is a summary you can share with the team before Thursday's meeting.
Four-Day Work Week: Pros and Cons for a 20-Person Agency
A 20-person creative agency asked whether moving from a five-day, 40-hour week to a
four-day, 32-hour week would hold up against client deadlines and billable targets.
The short answer: it can, with two conditions attached.
| Pros |
Cons |
| Recruiting edge in a market where competitors still run five days |
Client meetings compress into four days and can clash |
| Long weekends reduce Friday's usual drop in response quality |
Payroll and software costs stay fixed while scheduled hours drop |
| Meetings get trimmed by design, protecting focus time the other four days |
Urgent client fixes need a dedicated on-call rotation |
| Easy to reverse in a single department if the trial does not hold up |
Some clients may read a shorter week as reduced availability |
What Changes Operationally
Internal meetings currently run 6 hours a week per person, leaving 34 billable hours
out of the 40-hour week. Across 20 staff, that is 680 billable hours a week. A
four-day, 32-hour week with meetings trimmed to 4 hours a week would leave 28 billable
hours per person, or 560 across the team. Closing that 120-hour gap needs either a
small rate increase on new work or tighter scope on existing retainer hours.
Client-Facing Considerations
Twelve of the agency's 31 active clients are on retainers with same-day response
clauses. Those twelve need a short amendment covering Fridays and a rotation of two
people a week to handle anything urgent. The other 19 clients are project-based with
no same-day clause, so their contracts need no change for the trial to start.
Steps to trial it
- Pick one department of 6 to 8 people to run the four-day week for one full quarter.
- Set an on-call rotation so two people cover Fridays for that department only.
- Send the retainer amendment to the 12 affected clients two weeks before the trial starts.
- Track billable hours, response time and sick days weekly against the prior quarter.
- Review the results at week 12 and decide whether to extend the trial agency-wide.
Recommendation
Run the trial in one department first rather than switching the whole agency at once.
A 20-person agency has less room to absorb a weak quarter than a larger firm. A
single-department trial keeps the downside contained, and it still produces three
months of real data on billable hours and client response time.
Rendered in the Minimal theme. Open it in the editor to change the theme or the text.
The Minimal theme, and Slate as an alternative
The worked example above uses Minimal: quiet type at 16px with a 1.75 line height, a narrow column, and extra space between blocks. It suits an answer that is mostly prose with one table. If the document leans more on tables and lists, Slate fits better, with cool greys, blue links and a tighter base size built for exactly that shape.
Exporting the answer once it is styled
The export menu on the preview header covers four cases. "Print or save as PDF" opens the browser's print dialog, and choosing "Save as PDF" there is what saves the file. "Download .html" packages the answer as one standalone file, styling and fonts included. "Copy styled HTML" puts the document on the clipboard with its styles inlined, for pasting into an email or a CMS editor. List markers may not survive that trip. "Download .md" saves the source as written, unchanged.
Why this beats asking for a finished file
Asking any of them to also hand back a finished PDF or HTML page spends output tokens on that markup. It spends the same tokens again for every colour, font or layout change afterward. Generating the Markdown once and styling it here keeps those two costs separate. The assistant writes the words; the theme handles the design, as many times as the document needs it changed.
Questions
Does it matter which assistant wrote the answer?
No. If the answer arrived as Markdown, its source has no effect on how it renders or exports, local models included.
The assistant gave me formatted text with no visible symbols. Now what?
Ask it to answer in Markdown instead. You then get plain text with headings, pipes and backticks that this editor can render.
Why does the pasted answer sometimes start with an odd sentence?
Some assistants add a lead-in line such as "Here is a summary" before the Markdown proper starts. Delete that line in the editor before styling, or leave it as an intro.
Do I need to pick a different theme for a different assistant?
No. Themes style the document, not the assistant that wrote it. Pick a theme by what the document is, a report, a comparison, a set of notes, not by its source.