# PDF saving/printing from report viewer

**URL:** <https://forum.inductiveautomation.com/t/pdf-saving-printing-from-report-viewer/9352>\
**Category:** Ignition\
**Created:** [November 18, 2014, 4:06pm UTC](https://forum.inductiveautomation.com/t/pdf-saving-printing-from-report-viewer/9352 "2014-11-18T16:06:28Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![mmurphy](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mmurphy/32/11430_2.png) [@mmurphy](https://forum.inductiveautomation.com/u/mmurphy)\
**Post date:** [December 20, 2019, 7:39pm UTC](https://forum.inductiveautomation.com/t/pdf-saving-printing-from-report-viewer/9352/3 "2019-12-20T19:39:33Z")

</div>

Disregard my previous post! I found the answer here:

> [@Problem on Report Viewer Save as PDF (Saves 0 Bytes) HELP!](http://forum.inductiveautomation.com/t/problem-on-report-viewer-save-as-pdf-saves-0-bytes-help/15224/3):
>
> Hello, I had a similar problem, and contacted support, turns out the java applet was running out of memory. Paul asked me to do the following to confirm if this was the case. "The most likely cause for this is a lack of client memory; generating reports to save as PDF is relatively memory intensive and usually spikes client memory. If you open the client diagnostics window (Help -\> Diagnostics, or Ctrl + Shift + F7 if you have the menu bar hidden) then go into the ‘Console’ tab, there will pro…

Turns out my report was too big. I maximized the Client memory and it still wouldn't run. So I broke it up into multiple smaller reports. Now I'm good. 🙂

---

_[View the full topic](https://forum.inductiveautomation.com/t/pdf-saving-printing-from-report-viewer/9352)._
