How to Convert IPYNB to PDF

Choose the workflow

Use browser print when you want a quick, private PDF of content already saved in an `.ipynb` file. The workflow does not need Python, Pandoc, or a LaTeX installation, but it uses your browser's print dialog rather than creating a direct server-generated download.

Use Jupyter or nbconvert when you control the notebook environment and need a repeatable local publishing pipeline. That path can provide more template control, but it may need additional browser, Pandoc, or TeX dependencies depending on the export format.

Print a saved notebook locally

First run the cells whose charts, tables, and text output you need, then save the notebook. Select the file in the converter, inspect the preview, choose Full Notebook or Report mode, and select Print / Save as PDF. In the browser dialog, choose Save as PDF and inspect the resulting file before sending it.

Use Report mode when the audience needs explanations and results but not the code inputs. Use Full Notebook for a reproducible review copy that retains the code and saved outputs together.

Check the result before sharing

Look for long code lines, wide tables, page breaks, figures, and unsupported output notices. Enable wrapping, choose landscape orientation, or use a wider page setup when the preview makes the limitation obvious.

Interactive widgets and browser-dependent charts cannot become interactive PDF content. Save a static chart or other static representation in the notebook before converting it.

When a local toolchain is the better choice

Choose nbconvert when your team needs automation, source-controlled templates, or a local build step. Its PDF-oriented workflows have different requirements and failure modes from browser printing, so record the environment and test representative notebooks before using it for a course or report pipeline.