Since January 2926, PDF conversion doesn't pick up correct layout

[vischia]

Hi,

since January 2026, the conversion to PDF doesn't figure out slides in 16:9:

I have tried:

• downgrading node, npm, puppeteer (and consequently chrome), and decktape, even forcing an old version of puppeteer
• upgrading all the above to the latest version
• running the docker release

all to no avail.

Adding the -s option seems to have no impact on the result.

I cannot really understand what is happening (I suspect interaction with puppeteer and chrome): I don't really care having latest versions, I would live happily if the docker image or if the downgrade would work, but it doesn't.

Thank you very much in advance for any advice you may provide! I can give more details or logs of my attempts, if needed.

Cheers,
Pietro

[vischia]

(sorry, forgot to mention: I am on MacOS sequoia.

Last attempt I made was with:
node v21.7.3
nvm 0.40.3
npm 8.19.4
puppeteer 24.36.1
decktape 3.15.0

[astefanutti]

@vischia would you be able to share your presentation (or a minimal version) that'll help reproduce the issue?

[vischia]

Hello @astefanutti , sure: I am sharing an older presentation, where I have for comparison the PDF I generated correctly in May last year (for which now the generation fails with the same issue as the slides I mentioned above).

So:

• HTML deck
• PDF export from last May: it works: I include it in case the PDF metadata can help in tackling the issue). I generated it from my localhost webserver python -m http.server 8001
• PDF export from today same issue as in my post above. I obtain the same result if I generate it from my localhost webserver or from the external link I provide here.

I included both PDFs in case their metadata can help.

Thank you very much for your availability in checking this!

Cheers,
Pietro

[vischia]

Hello, were you able to take a look and reproduce the issue? Do you have any pointers?

Cheers,
Pietro

[astefanutti]

@vischia I've been able to reproduce on the latest Decktape version.

I haven't faced any issues with other remark.js presentations I've tested, so it would seem to be specific to your presentation.

Is there any particular layout related thing you're doing in your presentation that cause it to behave differently than the "official" remark.js example?