Skip to main content
Question

Print to PDF Issue

  • November 11, 2025
  • 5 replies
  • 48 views

jonajinga
Forum|alt.badge.img+2

Hi folks,

In Chrome and other Chromium based browsers there seems to be a print to PDF bug. When my users attempt to print an interface the print dialogue pops up as attempting to print 20k+ pages of records when the reality is that it should be somewhere between 7-10 pages only. Has anyone else encountered this issue?

5 replies

ScottWorld
Forum|alt.badge.img+35
  • Genius
  • 9808 replies
  • November 11, 2025

There are 2 print options: “Print This Page” and “Print All Records”. Are they choosing “Print This Page”? That option generates the smaller document.

- ScottWorld, Expert Airtable Consultan 


jonajinga
Forum|alt.badge.img+2
  • Author
  • New Participant
  • 3 replies
  • November 11, 2025

Thanks Scott, but that’s not it. I’m actually only printing a single record but the print dialogue says there are 20k+ pages in the record which is not correct. I’ve narrowed it down to Chrome and other Chromium based browsers since I can’t replicate the problem in Firefox or the Airtable desktop app itself.


ScottWorld
Forum|alt.badge.img+35
  • Genius
  • 9808 replies
  • November 12, 2025

Weird, I’m not seeing that on my end. You may want to email support@airtable.com about the issue.

- ScottWorld, Expert Airtable Consultant  


TheTimeSavingCo
Forum|alt.badge.img+31

Hm, what kind of layout are you using to print?  I just tried printing a List type Interface on Chrome 141 on a Mac and it worked fine (barring an extra page at the end)

Here’s the base I used and I got 18 pages.  If you also get 18 pages when you try this then we know it’s localized to your base / Interface, and if you don’t get 18 pages then it might be to do with your print settings?

If you could private message me a link to your base I could try printing from there too!


jonajinga
Forum|alt.badge.img+2
  • Author
  • New Participant
  • 3 replies
  • November 12, 2025

Thanks folks, this appears to have resolved itself on Chrome/Chromium based browsers.