Response Saver Guide
Markdown vs Plain Text for Saving AI Responses
Markdown and TXT are useful for different reasons, but the file extension alone does not tell you what happened to the text inside. In Response Saver, Markdown can receive Tool-generated structure such as note properties and a Markdown title. TXT and Copy omit those Tool-generated properties and use a plain title line.
If you are not sure whether one response is the right information unit to preserve, read Saving One AI Response vs Saving a Conversation: What Should You Preserve? first.
Choose based on the artifact you need
| Output | Tool-generated structure | Best fit |
|---|---|---|
| Markdown (.md) | Can add YAML note properties and a # Title | Notes, documentation, repositories, and editors that understand Markdown |
| Text (.txt) | No generated YAML properties; optional Title is a plain line | Simple portable text files and workflows that do not need generated note metadata |
| Copy | Same prepared text representation used for TXT | Pasting the prepared response into another destination |
TXT does not mean Markdown was stripped
Response Saver does not run the pasted body through a Markdown-to-plain-text parser. If the response already contains markers such as ##, **bold markers**, backticks, or list syntax, those characters can remain in the TXT file and copied text.
What Markdown can add
With a Title, the Markdown artifact normally adds # Title. If Add note properties is enabled and no leading frontmatter is detected, the Tool can generate YAML properties for title, date, type, source, and tags.
Those generated properties are not included in the visible preview, TXT download, or Copy output.
Existing frontmatter is a special case
When note properties are enabled and the prepared body begins with a pattern the Tool recognizes as frontmatter, the existing body is retained for Markdown instead of generating a replacement properties block. In that path, a separate Title entered in the UI is not prepended to the Markdown artifact.
This is bounded detection of a leading --- ... --- block, not a promise that the Tool validates arbitrary YAML.
Cleanup affects both representations
The prepared body is shared by Markdown and text outputs. Line endings are normalized, a leading BOM is removed, and outer whitespace is trimmed. Optional controls can remove an initial Assistant/ChatGPT label and normalize selected copied-list formatting outside fenced code. These are deterministic transformations, not semantic rewriting.
Review the actual artifact
Use Markdown when its lightweight structure or generated note properties are useful. Use TXT or Copy when you want the text representation without Tool-generated YAML properties or a Tool-generated Markdown title marker. In either case, inspect the result if exact syntax matters to the next system.
Try it with the Tool
Prepare one useful AI response as a local Markdown or text file.
Runs in this browser. No upload by this tool. Copy or download locally, then review before sharing.