# Obtain auspice phylogenetic tree in journal format

**URL:** <https://nextstrain.discourse.group/t/obtain-auspice-phylogenetic-tree-in-journal-format/461>\
**Category:** Uncategorized\
**Created:** [March 30, 2021, 6:49pm UTC](https://nextstrain.discourse.group/t/obtain-auspice-phylogenetic-tree-in-journal-format/461 "2021-03-30T18:49:20Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Amanda](https://avatars.discourse-cdn.com/v4/letter/a/67e7ee/32.png) [@Amanda](https://nextstrain.discourse.group/u/Amanda)\
**Post date:** [March 30, 2021, 6:49pm UTC](https://nextstrain.discourse.group/t/obtain-auspice-phylogenetic-tree-in-journal-format/461/1 "2021-03-30T18:49:20Z")

</div>

I generated a build for a set of SARS-CoV-2 data and would like to include the phylogenetic tree from the auspice json as a figure in a paper. How can I obtain the auspice json tree in pdf, jpeg, eps, etc. format? I’m not familiar with conversions between data formats and have just started using nextstrain. Many thanks in advance!

---

<div class="post-metadata">

**Author:** ![james](https://yyz1.discourse-cdn.com/flex031/user_avatar/nextstrain.discourse.group/james/32/11_2.png) [@james](https://nextstrain.discourse.group/u/james)\
**Post date:** [March 31, 2021, 12:07am UTC](https://nextstrain.discourse.group/t/obtain-auspice-phylogenetic-tree-in-journal-format/461/2 "2021-03-31T00:07:31Z")

</div>

You can obtain an SVG of the visualisation [via these steps](https://docs.nextstrain.org/en/latest/guides/share/download-data.html#svg-screenshot) and then tweak as needed for the publication. If JPEG is good enough then you can just take a screenshot 😉

---

<div class="post-metadata">

**Author:** ![Amanda](https://avatars.discourse-cdn.com/v4/letter/a/67e7ee/32.png) [@Amanda](https://nextstrain.discourse.group/u/Amanda)\
**Post date:** [March 31, 2021, 3:04am UTC](https://nextstrain.discourse.group/t/obtain-auspice-phylogenetic-tree-in-journal-format/461/3 "2021-03-31T03:04:57Z")

</div>

Thank you so much! I must have overlooked how to do that in the documentation. It’s always worth scrolling to the bottom of the page! 😉
