Exported PDF from Markdown is empty

[Divyansh200102]

Description:
When exporting a Markdown document as a PDF, the generated file is completely empty.

Steps to Reproduce:

1. Paste Markdown content into the editor
2. Export as PDF
3. Open the exported PDF file

Expected Behavior:
The PDF should contain the rendered Markdown content.

Actual Behavior:
The exported PDF is empty (no content is displayed).

Note: My markdown file is over 1300 lines long and this seems to be only happening for large markdown files . For small markdown files it's working as expected.

Screenshots:

[ThisIs-Developer]

Thanks for reporting this issue!

I’ve tested the PDF export feature using my own Markdown files, and it’s working correctly on my end. The PDF is generated with all content visible as expected.

If your Markdown does not contain any personal or confidential information, could you please share the file (or a minimal reproducible example)? That would help us investigate why the pages are coming out blank in your case.

Looking forward to your response so I can debug this further 👍

[Divyansh200102]

@ThisIs-Developer this seems to be happening for files with more than 1200 to 1300 lines . I checked for myself and it's working fine for files with over 1000 lines but a blank pdf starts coming with the lines starts hitting around 1300+ lines . Please let me know if you can reproduce it. You can probably use any dummy data for this and it should start showing up with the line number gets more than around 1300 or maybe it has something to do with the characters so I am not sure myself.

[ThisIs-Developer]

Oh, I see—okay, I’ll check it and update accordingly. Thanks!

Also, one more person mentioned this in #22 , but they couldn’t provide any input.

[D1360-64RC14]

I successfully reproduced with a 191 lines file (975 words, 7298 chars), but... I can't share it here.

Btw, I tried to create a shareable version replacing all the words with Lorem Ipsum, keeping the formatting, but, strangely, the Ipsum'ned version rendered properly, so ̄\_ (ツ)_/ ̄

The original file was written in Brazilian Portuguese.

[ThisIs-Developer]

I successfully reproduced with a 191 lines file (975 words, 7298 chars), but... I can't share it here.

Btw, I tried to create a shareable version replacing all the words with Lorem Ipsum, keeping the formatting, but, strangely, the Ipsum'ned version rendered properly, so ̄_ (ツ)_/ ̄

The original file was written in Brazilian Portuguese.

Thanks for reporting this issue.
The issue is related to how the markdown content is encoded into the share URL. For large files, especially with non-English characters like Brazilian Portuguese, the generated encoded/hash text becomes very large and can exceed practical URL length limits.

That also explains why the Lorem Ipsum version rendered correctly even with the same formatting — the content compresses differently and produces a much smaller encoded output.

I was able to face a similar issue myself with long markdown documents too.

[ThisIs-Developer]

Hi @Divyansh200102 and @D1360-64RC14, hope you are doing great.

It has been quite a while since this issue was created, and Markdown Viewer has evolved a lot since then with the help of the community.

Coming back to this issue: at that time, Markdown Viewer only had the custom PDF export method. Today, it also supports a browser-based PDF export option, so I decided to test it again with a much larger document - around 112,960 words and 749,984 characters.

When I used the browser-based PDF export, it took some time, and the browser became temporarily unresponsive a few times, but eventually the print preview opened successfully with around 660 pages, and the content was rendered correctly.

So currently, the two PDF export methods serve different needs:

• Browser-based PDF - better suited for very large documents.
• Precision PDF - better for smaller documents where more controlled formatting is preferred.

Because of this, I believe the original issue is effectively resolved now.

I’ll keep the issue open for a little longer and wait for confirmation from both of you before closing it. We’ve already waited this long, so I’m happy to wait for your confirmation as well.

Thank you both for your patience and for staying with Markdown Viewer as it continues to improve.