# Why is the PDF output from the history widget vectorized?

**URL:** <https://community.tulip.co/t/why-is-the-pdf-output-from-the-history-widget-vectorized/12078>\
**Category:** Product Suggestions\
**Created:** [July 30, 2024, 7:31am UTC](https://community.tulip.co/t/why-is-the-pdf-output-from-the-history-widget-vectorized/12078 "2024-07-30T07:31:53Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![sebme](https://avatars.discourse-cdn.com/v4/letter/s/439d5e/32.png) [@sebme](https://community.tulip.co/u/sebme)\
**Post date:** [July 30, 2024, 7:31am UTC](https://community.tulip.co/t/why-is-the-pdf-output-from-the-history-widget-vectorized/12078/1 "2024-07-30T07:31:53Z")

</div>

At present, if you try to print from a record history widget, the resulting output appears to be vectorized prior to being printed. What is the reasoning behind this?

As a result

- Printing long “batch records” can crash your workstation
- The resulting print output is no longer searchable

---

<div class="post-metadata">

**Author:** ![sebme](https://avatars.discourse-cdn.com/v4/letter/s/439d5e/32.png) [@sebme](https://community.tulip.co/u/sebme)\
**Post date:** [August 5, 2024, 10:11am UTC](https://community.tulip.co/t/why-is-the-pdf-output-from-the-history-widget-vectorized/12078/2 "2024-08-05T10:11:53Z")

</div>

Nobody cares or is it unclear what I mean by “vectorizing”? It essentially seems to turn the printout into something like an image rather than just spitting out some standard text…

---

<div class="post-metadata">

**Author:** ![Beth](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/beth/32/5987_2.png) [@Beth](https://community.tulip.co/u/Beth)\
**Post date:** [August 5, 2024, 5:35pm UTC](https://community.tulip.co/t/why-is-the-pdf-output-from-the-history-widget-vectorized/12078/4 "2024-08-05T17:35:08Z")

</div>

Hi @sebme - we definitely care, but thank you for the clarification! I had to check with the Tulip product team that owns this to make sure I could answer this correctly.

Basically, there isn’t a strong reason for this other than it was how it was originally implemented many, many years ago 🙂 Unfortunately, changing anything related to printing would require a heavy technical lift that we currently cannot prioritize. Realistically, we’ll only be able to work on this once we implement a new review experience (which should hopefully happen next year).

---

<div class="post-metadata">

**Author:** ![sebme](https://avatars.discourse-cdn.com/v4/letter/s/439d5e/32.png) [@sebme](https://community.tulip.co/u/sebme)\
**Post date:** [December 20, 2024, 10:24am UTC](https://community.tulip.co/t/why-is-the-pdf-output-from-the-history-widget-vectorized/12078/5 "2024-12-20T10:24:35Z")

</div>

Thank you, @Beth. Can you have someone please check this again… I mean… look at this: Someone wanted to check a trail and does not have access to any of the workstations… This is what we have to send around… IF it actually get’s finally exported/printed at all.

And on top of that nobody can search it for any data in the end because of the vectorization.

Idea: Just please give us a HTML view of the output with all data with a simple print-ready CSS 🙄

 ![image](https://us1.discourse-cdn.com/flex020/uploads/agilemfg/original/2X/b/b3801bef902f54533ec32da557f0115d475b80bc.png)