Tab & Tap
English
In the Chrome Web Store

IPYNB to PDF help and support

Fixes for the most common problems when converting a Jupyter notebook to PDF with IPYNB to PDF. If your problem is not here, email support and we will look into it.

Email support →support@tabandtap.com

First things to try

  1. Reload any GitHub tab that was open before you installed the extension.
  2. Open the converter from the toolbar icon and drop the .ipynb file on the page.
  3. In the print dialog, set the destination to “Save as PDF”.
  4. Check page size, orientation and Show code in the PDF settings before you save.
  5. If a GitHub notebook will not download, use “Download raw file” on GitHub and drop the file instead.

Common problems and fixes

Download PDF button doesn't show on GitHub

Reload the GitHub tab: tabs that were open before you installed the extension do not get the button until they are reloaded. The button appears only on a notebook file page (an address with /blob/ that ends in .ipynb), next to Raw, or in the lower right corner when GitHub shows no Raw button.

“Notebook not found on GitHub” for a private repository

The extension downloads the notebook with your GitHub sign-in, so sign in to GitHub in the same Chrome profile and try again. If it still fails, open the file on GitHub, use “Download raw file”, and drop the .ipynb on the converter page.

“This file is a Git LFS pointer” error

The repository stores the notebook in Git LFS, so the file the extension got is only a small pointer. On GitHub, use “Download raw file” to get the real .ipynb, then drop it on the converter page.

“This file is not valid JSON” or “not a Jupyter notebook”

The file is damaged, cut off, or not a notebook. Open it in Jupyter, JupyterLab or VS Code and save it again, or download it again from where it came from. A notebook must be JSON with a “cells” list.

“Unsupported notebook version” error

Only nbformat 3 and 4 notebooks are supported. Open the notebook in a current Jupyter and save it, which upgrades it to nbformat 4, then convert it again.

The PDF has the date and a chrome-extension:// address on each page

Set Margins back to Default in the print dialog. The converter sets the page size, orientation and margins so that Chrome has no room for its own headers and footers; changing the margins in the dialog can bring them back, and then you can also clear Headers and footers under More settings.

A chart or widget is missing from the PDF

A PDF cannot hold interactive output, so widgets and charts without a saved static image show “Interactive output omitted”. Save a static image of the chart in the notebook (for example a PNG export), run the cell, save the notebook and convert it again. Images linked from the web are not loaded and show “External image not loaded”.

A large notebook is slow to convert

Files over 50 MB show a warning but are still converted, which can take a while. Notebooks are mostly large because of embedded images; clearing outputs you do not need in Jupyter makes the file smaller.

Only one of my notebooks was converted

The converter takes one notebook at a time. When you drop several files it converts the first one and says which; drop the next file after you save the PDF.

Your data

IPYNB to PDF keeps only your PDF settings (page size, orientation, show code, In/Out numbers, file name as title and the page footer) in Chrome’s synced extension storage, so they follow you to other computers where you are signed in to Chrome with sync on. Notebooks are never saved: they are read in the converter tab and gone when you close it. There is nothing to back up. To reset the settings, change them back in the popup, or remove the extension, which deletes them.

Privacy policy of the extension →

When you write to us

  • The exact error message the converter showed.
  • Where the notebook came from (your computer, a public or private GitHub repository, Colab or Kaggle) and its size.
  • What is wrong in the preview or the PDF, for example which cell or output looks different from Jupyter.
  • If you can share it, a small notebook that shows the problem (optional).
  • The extension name and its version from chrome://extensions.
  • Your Chrome version from chrome://settings/help and your operating system.
  • What you did, what you expected and what happened instead.
  • A screenshot, if the problem is visible on the screen.
Email support →support@tabandtap.com