DEV Community: Chest Nuts

How to Turn a ChatGPT Share Link into a PDF (and What’s in the Snapshot)

Chest Nuts — Mon, 02 Nov 2026 04:19:15 +0000

Someone sends you a ChatGPT share link: a teammate's research, a teacher's worked example, or a client brief. You want a clean file you can read offline. Before you save it, understand who can open the link and what happens when you export a copy.

What a ChatGPT share link contains

A shared conversation link is a view of selected ChatGPT content. Current conversation links start with https://chatgpt.com/share/.

OpenAI says that for personal accounts, anyone with the link can view the shared content. The link shows the content available when it was created or last updated; later messages are not added automatically. Links created in managed workspaces may be limited to eligible members of that workspace. See the OpenAI Help Center guide to shared links.

Think of a personal share link as a snapshot that can be forwarded, not as a private document or a live window into the owner's account.

Two checks before you convert a link

Check the contents. A personal link can be opened by anyone who gets it, and there are no recipient-by-recipient access controls. Read the shared preview first and remove names, account details, API keys, or other private information before creating a link. If someone sent you the link, make sure they intended the conversation to be shared with you.

Remember that links and files can be copied. The owner can update or delete a shared link. Deleting it stops future access through that URL, but it does not remove a copy another person already imported into their ChatGPT history. A PDF or Word export is also a separate file that can be forwarded, so store it with the same care as the conversation.

Choose a way to save it

Print the page to PDF

For a short, mostly text conversation, open the share link and use your browser's Print → Save as PDF. It is quick and needs no extra tool. Long chats, wide tables, code, and equations can break across pages or lose formatting, so review the result before sending it on.

Copy it into a document

For a few short messages, copying the visible text into Word or Google Docs gives you control over the final layout. Tables and formulas may need manual cleanup.

Convert the share link

If the conversation has tables, code, or math, a converter can save the cleanup work. With TODOC's ChatGPT share link converter, paste a public share URL, load the conversation into the editor, remove turns you do not need, then export to PDF, Word, or Excel. The converter currently accepts ChatGPT share links only.

TODOC processes the conversion on its server. Its privacy policy says source content is not retained separately after conversion and is not used to train AI models; exported files are kept according to the export-history period for the selected plan. Check that policy before using the service with work or client material.

A simple workflow

Open the shared conversation and review what it contains.
Choose Print for a short, simple chat, or use a converter when tables, code, or equations need to remain readable.
Review the exported file, then keep it somewhere with the right access controls.

If the link does not open, ask the owner to check whether the chat or link was deleted, or to create or update a link. The OpenAI shared-link guide explains how owners manage those links.

Disclosure: I'm the developer of TODOC, the converter mentioned above. Printing or copying a conversation works without it.

How to Convert Markdown to Word Without Breaking Tables and Math

Chest Nuts — Wed, 28 Oct 2026 08:08:51 +0000

You write in Markdown. Someone else wants a Word document. Usually that's fine, until the file has a table, an equation, or a code block, and the .docx you send comes out looking broken.

This guide shows how to convert Markdown to Word properly, mostly with pandoc, and covers the problems I ran into after doing it a lot.

The one-liner

If you have pandoc installed, a basic Markdown to Word conversion is one command:

pandoc notes.md -o notes.docx

Headings become real Word heading styles (so the navigation pane and table of contents work), lists become real lists, and pipe tables become Word tables. For a plain document, you can stop here.

Make it look like your documents: the reference doc

The default output uses pandoc's built-in styles. To match your company or school template, generate the reference file, edit its styles in Word, and pass it back:

pandoc -o reference.docx --print-default-data-file reference.docx
# open reference.docx in Word, change the styles (Heading 1, Normal, Table...), save
pandoc notes.md --reference-doc=reference.docx -o notes.docx

Only the styles in reference.docx are used, not its content. If a change doesn't show up, you probably edited the text formatting directly instead of modifying the style.

Math: get real Word equations, not images

This is where most Markdown to Word converters fail. Pandoc's docx writer turns TeX math into native Word equations (OMML), so the equation stays editable in Word. You just have to make sure pandoc recognizes the math first.

Pandoc's Markdown understands $...$ and $$...$$ by default. But a lot of Markdown in the wild, including what you copy out of ChatGPT, uses $...$ and \[...\]. Enable that explicitly:

pandoc -f markdown+tex_math_single_backslash notes.md -o notes.docx

Two gotchas worth knowing:

Dollar signs that are prices. Pandoc only treats $...$ as math when the opening $ has a non-space character right after it, and the closing $ has a non-space character right before it and is not followed by a digit. That rule keeps It costs $5 and $10 as text, but documents that mix prices and formulas on the same line can still trip it up. The safest habit is to escape prices as \$5.
Display math inside lists. $$ blocks indented inside a list item sometimes get parsed as part of the paragraph. Put a blank line before and after the block.

Tables

Pipe tables convert fine:

| Plan    | Price | Change |
|---------|------:|-------:|
| Basic   |  $9   |   +4%  |
| Pro     |  $29  |  -2%   |

Things to watch:

Column widths. Pandoc lets Word auto-size the columns. Wide tables with long text can overflow the page; set widths in your reference doc's table style, or fix them by hand in Word.
Line breaks in cells. Pipe tables can't hold multi-paragraph cells. Use <br> for a line break, or switch to pandoc's grid tables if you need real paragraphs.
Numbers. In Word a number in a table is just text. If the reader is going to sum the column, they want Excel, not Word.

Code blocks

Fenced code blocks with a language tag keep a monospace font and get syntax highlighting in the .docx:

```python
def growth(start, end, years):
    return (end / start) ** (1 / years) - 1
```

Always add the language tag. Without it you get a plain monospace block, which is fine but harder to read.

Mermaid diagrams

Pandoc doesn't render Mermaid. Inside the .docx you'd just see the source code. Render diagrams to images first with mermaid-cli, then reference the image:

npx -p @mermaid-js/mermaid-cli mmdc -i flow.mmd -o flow.png

![Signup flow](flow.png)

Tall diagrams (vertical flowcharts) can run off the bottom of the page. Add a height attribute so pandoc scales them by height: ![Signup flow](flow.png){height=8in}.

A full command

Putting it together:

pandoc notes.md \
  -f markdown+tex_math_single_backslash \
  --reference-doc=reference.docx \
  -o notes.docx

The no-install option

If you don't want to set up pandoc, or you need to hand this to non-developer colleagues, I built a browser tool for exactly this: a Markdown to Word converter where you paste Markdown, check the preview, and download a .docx. It runs the same kind of pipeline on the server, with the math delimiter handling, table sizing and Mermaid rendering above already done for you. Your first export doesn't need an account.

Checklist

[ ] -f markdown+tex_math_single_backslash if your source uses $ $
[ ] Escape $ when it means money
[ ] Blank lines around $$ blocks
[ ] Language tag on every code block
[ ] Mermaid rendered to PNG before conversion
[ ] --reference-doc for house styles

What breaks for you when you convert Markdown to Word? I'm collecting edge cases, so drop them in the comments.

Disclosure: I'm the developer of TODOC, the converter mentioned in the "no-install option" section. Everything else in this post works with plain pandoc.

A practical workflow for stronger product creative: clean images, then plan short videos

Chest Nuts — Wed, 28 Oct 2026 04:29:17 +0000

Product creative often starts with two questions: can someone understand the product image at a glance, and does the short video earn attention in its opening seconds? A useful workflow treats those as connected steps: prepare a clear visual asset, then plan an original short-form story around it.

1. Make the product image easier to reuse

For a product listing, ad concept, or social post, a clean cutout can make it easier to place the same product on different backgrounds. ZeroBG removes image backgrounds and can return a transparent PNG or a solid-color background. Review fine edges—especially hair, glass, shadows, and reflective objects—before using the result in a campaign.

2. Study the structure of a short video, not its footage

A useful reference is a video whose pacing fits the story you want to tell. Fypzo analyzes public TikTok and YouTube Shorts links and breaks down elements such as the opening hook, beat structure, shot list, pacing, captions, sound, and transcript. It can then help turn that structure into an original script or shooting guide, and create template videos from product photos.

The important distinction is to learn from the sequence of ideas—not to reuse someone else’s footage, music, or wording.

3. Bring the two steps together

Prepare one clean product image and check the cutout at full size.
Pick a relevant short-video reference and note what each beat contributes: context, demonstration, proof, or next step.
Write a new hook and shot plan for your own product.
Use your own screenshots, product photos, and footage; check every generated caption and claim.
Test one change at a time, such as the opening line or the order of the demonstration.

This workflow can make creative production more organized, but it cannot guarantee reach or conversions. Treat generated scripts and visuals as drafts, and verify them before publishing.

Tools: ZeroBG · Fypzo

Disclosure: This article was prepared with AI assistance. Product descriptions are based on the tools’ public websites; this is not an independent performance test.

Exporting AI-Generated Technical Content Without Losing Structure

Chest Nuts — Thu, 22 Oct 2026 07:33:13 +0000

AI assistants often return content that looks like a document but is really a mixture of Markdown, code fences, tables, LaTeX, and sometimes Mermaid. Moving that mixture into Word or PDF is more than copying text: each structure needs a useful representation in the destination format.

A small test case

Imagine an answer with a heading, a two-column decision table, a fenced code example, an equation, and a flowchart. A plain paste may preserve the words while losing hierarchy. The heading may stop being navigable, the table may become tab-separated text, and math may be flattened into characters or an image.

The right question is not “Did the export finish?” It is “Can the reader still use each part of the result?”

What to verify

Headings: Do they form a clear hierarchy in the final document?
Tables: Are cells, columns, and long values readable? If the table is the deliverable, would a spreadsheet be better?
Code: Are indentation, line breaks, and symbols intact?
Math: Is the equation legible, and does it remain usable for the intended editing workflow?
Diagrams: Does the diagram survive as a clear visual at normal reading size?
Links: Do they point to the intended pages after export?

For a repeatable check, keep a short “stress test” answer with all of these elements. Export it whenever you change tools or document templates. That is more informative than testing with a single paragraph.

A practical workflow with TODOC

TODOC provides a web editor that can take pasted AI content, let you review it, and export Word, PDF, or Excel files. Its Chrome extension adds export controls to ChatGPT, Claude, Gemini, and DeepSeek and also supports Markdown output. The site specifically calls out tables, code, LaTeX math, and Mermaid diagrams as content it handles.

I would still inspect the resulting file. Format preservation reduces cleanup, but technical documents deserve a final human pass: check the rendered equation, look at any wide table, and confirm that code is copyable. Export tools solve the structural transfer problem; they do not replace technical review or fact-checking.

A Practical TikTok Shop Creator Brief: Hooks, Proof, and Shot Lists

Chest Nuts — Tue, 20 Oct 2026 03:02:17 +0000

A creator brief works best when it describes the evidence a viewer needs, not every word the creator must say. For TikTok Shop sellers, that distinction matters: a rigid script can make ten videos feel identical, while an empty brief leaves creators guessing about the hook, product demonstration, and claim boundaries.

1. Define the viewer and the proof

Start with one sentence about the viewer's problem. Then list two or three things that must be visible on camera. A gadget brief might require a real use case, a close-up of the result, and a shot that shows the product's size. If you cannot verify a claim, do not put it in the brief.

2. Offer hook options

Give creators multiple openings to test:

Result first: show the outcome before explaining the product.
Problem first: show the inconvenience that makes the product useful.
Question first: ask something a likely buyer already wonders.

These are creative starting points, not guarantees of reach. Let the creator choose the delivery that fits their audience.

3. Write a shot list, not a script

A five-part guide is often enough: opening visual, product reveal, hands-on demonstration, proof or result, and call to action. Specify any required disclosures or accurate product details. Leave room for the creator's voice.

4. Learn from references without copying them

When you study a successful short video, note the first visual, the sequence of beats, shot lengths, captions, and the moment the product appears. Reuse that structure for your own product, while shooting original footage and writing original copy. Fypzo is a tool we build to help with this process. It analyzes public TikTok and YouTube Shorts links into hooks, beats, shot lists, pacing, captions, and timed transcripts, and can turn that structure into a script and shooting guide based on your product.

5. Improve the next brief

After creators post, compare the videos. Which opening made the product clear quickly? Which demonstration actually showed the benefit? Which brief instructions produced awkward or repetitive content? Use those observations to refine the next round. More samples can expand distribution, but better feedback can make each sample more useful.

From Reference Video to Original Shot List: A Fypzo Workflow for Product Demos

Chest Nuts — Mon, 19 Oct 2026 08:17:21 +0000

When a product team says “make a video like this one,” the request is often too vague to film. The useful part of a reference is its structure: how it opens, what each shot establishes, how long a viewer waits for proof, and where the call to action appears. Here is a repeatable way to turn that structure into an original brief.

1. Define the claim before choosing a reference

Pick one product and one claim you can show. A phone accessory might need to demonstrate setup time, desk stability or portability. Write the proof shot first. If the claim cannot be verified in your own footage, do not make it in the video.

2. Extract the reference's decisions

Fypzo says its analyzer accepts public TikTok and YouTube Shorts links and labels the hook, story beats, shots, pacing, captions and sound, and timed transcript. That gives you a checklist to inspect. Ask: Does the reference open with the result or the problem? When does the product first appear? Which shot actually proves the benefit? Is there a pause before the call to action?

Treat the output as a planning aid. Check the underlying video yourself. A reference's view count does not establish that its approach will work for a different product or audience.

3. Build a new shot list

For a hypothetical compact charger, the brief could be:

Beat	Original footage to film	Purpose
Problem	A travel bag with multiple bulky adapters	Show the situation
Reveal	Your charger next to a phone for scale	Identify the product
Demo	Plug it into a real outlet and device	Show the action
Proof	A readable charging indicator and port close-up	Support a narrow claim
CTA	The product and one clear next step	Finish without overpromising

Replace this example with the real product's capabilities, setting and audience. Do not reuse the reference creator's footage, audio, person or unverified claims.

4. Turn the brief into production choices

Fypzo also describes a product-specific script and shooting guide with three hook options and a shot list. Its site lists optional template videos and AI-motion videos. These are separate production choices; a text brief is useful even if you decide to film every shot yourself. Before publishing, review every line for factual accuracy, remove unsupported superlatives and ensure captions are readable on a phone.

5. Learn from the published result

Test one variable at a time, such as the first two seconds. Keep the product demo and call to action stable so you can interpret the comparison. Use your channel's analytics to judge whether the video reached the right buyers, not just whether it collected views.

The result is a creative brief that someone else on the team can film and review. The reference supplies a useful pattern; the product supplies the evidence. Fypzo's official site describes the analyzer and creation options used in this workflow.

From AI Markdown to Reviewable Technical Docs: A TODOC Export Checklist

Chest Nuts — Sat, 17 Oct 2026 05:57:04 +0000

AI-generated documentation often contains more than prose: headings, fenced code, tables, LaTeX equations and Mermaid diagrams. Moving that structure into a document is a separate task from generating the answer.

TODOC offers a web editor and browser extension for this handoff. The public site lists Word, PDF and Excel export, while the extension also lists Markdown and support for ChatGPT, Claude, Gemini and DeepSeek. This article presents a practical review workflow based on those advertised capabilities, checked on October 17, 2026.

1. Start with a small, structured source

Before exporting a long specification, prepare a representative sample. Include the structures your actual documentation needs:

A clear document title and two heading levels.
A short code block with its language specified.
A table with explicit column names and units.
One equation or Mermaid diagram, if relevant.

For example, a deployment note could contain a service overview, a dependency list, a configuration table and a sequence diagram. Use illustrative values rather than production credentials.

2. Choose the handoff format

Use Word when reviewers need to edit the narrative or add comments. TODOC describes carrying headings, styles, tables and images into DOCX.

Use PDF for a fixed-layout handoff, such as a reviewed architecture note or training handout. Inspect page breaks and wide tables at the intended reading size.

Use Excel when the useful output is a structured table: test cases, task lists or a comparison matrix. Exporting a table does not validate its data, infer the right units or prove that its calculations are correct.

Use Markdown, listed for the extension, when the document belongs in a repository or text-based knowledge workflow. Review code and links as you would any other generated contribution.

3. Understand diagram and math handling

The website describes Mermaid diagrams being embedded as images in Word and PDF. That is useful for portability, but an image in a document is different from editable diagram source. Keep the original Mermaid text alongside the exported file if future changes matter.

TODOC also advertises LaTeX math support in Word and PDF. Include representative expressions in your trial export: subscripts, fractions and matrices may exercise different parts of a math workflow. Check the output against the intended notation rather than relying only on the source looking correct.

4. Review in the editor, then review the file

The web workflow is straightforward: paste an AI response or Markdown, refine it in the live editor and export. The extension offers an alternative directly on supported AI chat pages; current installation details are on the extension page.

Before downloading, remove conversational filler, repair heading hierarchy and verify references. After downloading, check the actual deliverable:

Are code indentation and symbols readable?
Do tables retain the correct row-to-column relationships?
Are diagrams legible and equations accurate?
Does the document make sense without the original chat?

5. Keep export quality separate from factual quality

A clean document can still contain a fabricated API option or an outdated instruction. Verify commands, dependencies and technical claims using the relevant primary documentation. Treat export as a formatting and handoff step, not as technical validation.

The site's current free-entry offer includes one export without signup and two daily exports after signing in. Check current limits before a large batch.

Explore the product at todoc.ai.

Disclosure: AI-assisted product article prepared for TODOC promotion. Product features above are described by the public website; this is not an independent export benchmark.

A Shot-by-Shot Planning Workflow for SaaS Demo Videos with Fypzo

Chest Nuts — Fri, 16 Oct 2026 10:36:23 +0000

A software demo can show a working feature and still leave viewers wondering why it matters. Before recording another screen walkthrough, define the problem, the proof, and the action you want a viewer to take.

This guide uses Fypzo as an example of a tool for studying short-video structure. It describes a planning workflow based on the product's public feature descriptions, rather than a performance test.

1. Start with one visible user problem

Choose a task your product actually solves: finding an overdue invoice, turning notes into a document, or comparing two versions of a file. Record the exact starting state and the expected result. Avoid leading with a tour of every menu.

An illustrative hook for a document app could be: “Your meeting notes are ready. Your client report is not.” The next shot should make that mismatch visible.

2. Analyze a reference as a sequence of decisions

Fypzo describes an analyzer that accepts public TikTok and YouTube Shorts links and breaks down hooks, story beats, shots, pacing, captions, sound, and a timed transcript. Its free analyzer is linked from the official site.

Use a reference to answer concrete questions: What appears in the first frame? When does the result become visible? Which shot supplies evidence? Where does the explanation slow down? Check the analysis against the source video before relying on it.

A reference's view count is context, not proof that its structure will work for your audience.

3. Turn the structure into an original shot plan

For a fictional document app, a brief could look like this:

Beat	Visual	Purpose
Problem	A page of messy sample notes	Establish the task
Action	A short screen recording of the relevant feature	Show what the user does
Proof	The resulting report beside the source notes	Make the outcome inspectable
Limitation	Highlight a detail that still needs review	Set an honest expectation
Next step	One clear invitation to try the workflow	Give viewers a useful action

Use synthetic sample data and remove private customer information from recordings. Keep cursor motion deliberate and captions readable on a phone.

Fypzo also describes product-specific remix scripts and shooting guides. Treat any generated script as a draft: verify every feature claim and replace generic promises with evidence you can actually show.

4. Test one creative variable at a time

Record two openings for the same demo while keeping the feature, main footage, and call to action consistent. Compare the resulting viewer behavior in your publishing platform's analytics. Define the metric before you post; more views alone may not indicate more qualified interest.

This is a proposed experiment, not a claim of measured improvement from Fypzo.

5. Keep the finished video yours

Study the order of information, then write original copy and create your own screen recordings. A public reference is not automatic permission to reuse its footage, music, voice, or branding. For generated media, inspect the result for errors before publishing.

Fypzo may be useful when you can describe the product but need a clearer creative brief. The practical output to aim for is a small, filmable plan with one promise and visible proof.

Official product information: fypzo.com. Analyzer: Viral Video Analyzer.

Disclosure: This article was prepared with AI assistance. Product descriptions are based on Fypzo's public website; the illustrative demo is fictional and no conversion or virality results are claimed.