# Table truncated during export to PDF bug **URL:** \ **Category:** Bugs\ **Created:** [September 1, 2025, 1:48am UTC](https://connect.superhuman.com/t/table-truncated-during-export-to-pdf-bug/57129 "2025-09-01T01:48:08Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![James\_Pawluk](https://yyz1.discourse-cdn.com/coda1/user_avatar/connect.superhuman.com/james_pawluk/32/29253_2.png) [@James\_Pawluk](https://connect.superhuman.com/u/James_Pawluk)\ **Post date:** [September 1, 2025, 1:48am UTC](https://connect.superhuman.com/t/table-truncated-during-export-to-pdf-bug/57129/1 "2025-09-01T01:48:08Z")
I’m still getting a bug reported elsewhere (and marked as fixed, hence starting a new topic): - [Graphical bug on table when exporting to PDF](https://connect.superhuman.com/t/graphical-bug-on-table-when-exporting-to-pdf/47422) - [PDF Export - Cut off - #4 by Ed\_Liveikis](https://connect.superhuman.com/t/pdf-export-cut-off/25058/4) It’s the last record in a table that is being truncated: ![image](https://global.discourse-cdn.com/coda1/original/3X/3/d/3d0cd39d8d10fdd9c47e0dd7ef7f889c74299d52.png) Compared to what it looks like on the page: ![image](https://global.discourse-cdn.com/coda1/original/3X/9/d/9d9f04d7e11e6f9bf3e085f494f1b64c5ef7b112.png) ![image](https://global.discourse-cdn.com/coda1/original/3X/9/d/9d9f04d7e11e6f9bf3e085f494f1b64c5ef7b112.png) ---
**Author:** ![James\_Pawluk](https://yyz1.discourse-cdn.com/coda1/user_avatar/connect.superhuman.com/james_pawluk/32/29253_2.png) [@James\_Pawluk](https://connect.superhuman.com/u/James_Pawluk)\ **Post date:** [September 1, 2025, 1:59am UTC](https://connect.superhuman.com/t/table-truncated-during-export-to-pdf-bug/57129/2 "2025-09-01T01:59:05Z")
Update: it appears it’s not just the last record. I changed the order of the two records I shared in the examples above, and the record that was now last wasn’t visible at all and the now second-last record still truncates. ![image](https://global.discourse-cdn.com/coda1/original/3X/f/b/fbf475b4071cefd5da7bc61fa136df9ae3a966b9.png) ---
**Author:** ![Konrad\_Mertner](https://yyz1.discourse-cdn.com/coda1/user_avatar/connect.superhuman.com/konrad_mertner/32/47936_2.png) [@Konrad\_Mertner](https://connect.superhuman.com/u/Konrad_Mertner)\ **Post date:** [September 2, 2025, 7:21am UTC](https://connect.superhuman.com/t/table-truncated-during-export-to-pdf-bug/57129/3 "2025-09-02T07:21:01Z")
it’s an annoying bug. You may have more luck using the browsers printing dialogue. > [@Printing in Coda: My Love Story With a Plot Twist broken\_heart](https://connect.superhuman.com/t/printing-in-coda-my-love-story-with-a-plot-twist/56931): > > I work with a lot of design studios, and I always start them off on Coda because, let’s be honest, it’s the BEST. trophy But… there’s this one tiny, stubborn plot twist in our love story: printing/exporting to PDF. Right now, I’m trying to export a table with 122 rows. Sounds simple, right? Well… every time I export: I never get the same number of rows/cards twice. It has never once exported all of them. Tried table view instead of card view—same sad ending. I’m not a coder, but… ---
**Author:** ![joost\_mineur](https://yyz1.discourse-cdn.com/coda1/user_avatar/connect.superhuman.com/joost_mineur/32/30539_2.png) [@joost\_mineur](https://connect.superhuman.com/u/joost_mineur)\ **Post date:** [September 17, 2025, 1:24pm UTC](https://connect.superhuman.com/t/table-truncated-during-export-to-pdf-bug/57129/4 "2025-09-17T13:24:47Z")
I have been using the CloudConvert pack and never looked back. The pack is free to use and the 3rd party service has a free tier that will do for occasional printing. I have documented how to print pages or tables by using this pack. Most suitable for repetitive tasks, but so easy to setup that even the occasional (pdf) print job is easy to handle. > [@Create PDF with a button](https://connect.superhuman.com/t/create-pdf-with-a-button/56061): > > Hello fellow doc makers, Over the years it has been asked many times: a button function to create a PDF file. Coda has a native “print & pdf” function, but for occasional users it is hard to find and you have to define some parameters for every print job, which might be be easy for regulars, but not that easy for many of your users. I have used this native print function a zillion times, but, apart from setting the options over and over, the real pain has been designing your pages (and sub-pag… Greetings, Joost ---
**Author:** ![Lisa\_Doucet2](https://yyz1.discourse-cdn.com/coda1/user_avatar/connect.superhuman.com/lisa_doucet2/32/41593_2.png) [@Lisa\_Doucet2](https://connect.superhuman.com/u/Lisa_Doucet2)\ **Post date:** [September 23, 2025, 7:02pm UTC](https://connect.superhuman.com/t/table-truncated-during-export-to-pdf-bug/57129/5 "2025-09-23T19:02:31Z")
This table truncation during PDF export is such an annoying bug. Konrad Mertner suggested using the **Print** option in the Opera browser, which worked well enough for **my** needs, but it’s definitely not an ideal solution for other users of my docs. There’s so much I love about Coda, but this issue is really difficult to defend to employers and clients. Something as basic as exporting a complete PDF shouldn’t be this complicated. ---
**Author:** ![Konrad\_Mertner](https://yyz1.discourse-cdn.com/coda1/user_avatar/connect.superhuman.com/konrad_mertner/32/47936_2.png) [@Konrad\_Mertner](https://connect.superhuman.com/u/Konrad_Mertner)\ **Post date:** [September 30, 2025, 11:44am UTC](https://connect.superhuman.com/t/table-truncated-during-export-to-pdf-bug/57129/6 "2025-09-30T11:44:46Z")
In my opinion Coda should implement a formula in which we can set orientation, paper size etc…