Talk to a human.

Email is the only channel

Write to support@ipynbtopdfconverter.com. There is no phone line, no chat widget and no support portal to log into.

There is deliberately no form on this page. A form needs a server-side endpoint, and in practice that means a third-party service holding your message — the same reason the converter has no upload button. An email client leaves the message, and the choice of what to send, with you.

If something did not convert correctly

The most useful reports name the notebook source and kernel (Jupyter, JupyterLab, Google Colab, Kaggle, Deepnote or the VS Code extension; python, R, julia, SQL or JavaScript), roughly how many cells the notebook has, and which output type came out wrong — a figure, a table, a matrix of LaTeX, a traceback, an image attachment.

Add the page settings used (A4 or US letter, portrait or landscape, light or dark, code and outputs on or off) and whether you downloaded the PDF or used print → save as PDF, since those two routes render the same document in different ways. If a message appeared on the progress line, paste its exact text — that one line usually identifies the cause.

Finally, your browser and version and your operating system, because the conversion runs in the browser and behaves differently on each engine.

If the layout is the problem

Describe what you expected rather than only what happened: a heading that should have stayed with its paragraph, a table split at the wrong row, a figure scaled smaller than it needed to be, a page that ended early with room left below.

A screenshot of the preview and the notebook name is usually enough to reproduce the issue. Where a specific cell is responsible, the ideal report is the smallest notebook that still shows the problem — three or four cells, with the output that misbehaves.

Security and privacy of your files

The converter never uploads a notebook, so nothing has to be sent to us to reproduce a problem. Email is not a private channel, and a message stays on servers we do not control.

Please do not attach notebooks containing client data, credentials, personal data or anything under an NDA. If a problem genuinely cannot be described in words or a screenshot, build a small test notebook that reproduces it with toy data instead — it is faster to diagnose and safe to send.

Bug reports, corrections and requests

A bug report that lists numbered steps to reproduce the problem is worth more than a long description of it. Say what you did, what you expected, and what the page did instead.

Corrections are welcome too — particularly where the guide or the FAQ disagrees with your own installation of Jupyter, Colab, nbconvert or TeX, since those tools change between versions. Feature requests are read, but the roadmap is intentionally short: anything that would require a server to store or process a notebook is unlikely to be added.

When to expect a reply

The site is maintained alongside other work, so replies are best effort, typically within a few business days. There is no 24-hour support promise and no paid tier that would change that.

If your question is already answered on the page, the answer will be a link to it — the FAQ covers file formats and the Colab and VS Code routes, and the guide walks through the conversion end to end.

What this channel cannot do

We can help with the converter, not with the notebook. A cell that raises an exception in Jupyter raises the same exception in the PDF, and debugging a model, a query or a dependency conflict sits outside what this site does.

Nor can anything be recovered from a conversion that finished: no copy of a notebook or a PDF is kept here, so a PDF that was never downloaded is gone, and re-converting the original file is the only route back to it.