# Generate a url for fastlane snapshot html output

**URL:** <https://discuss.bitrise.io/t/generate-a-url-for-fastlane-snapshot-html-output/2284>\
**Category:** Steps\
**Created:** [July 17, 2017, 1:53pm UTC](https://discuss.bitrise.io/t/generate-a-url-for-fastlane-snapshot-html-output/2284 "2017-07-17T13:53:27Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![jarryd](https://avatars.discourse-cdn.com/v4/letter/j/898d66/32.png) [@jarryd](https://discuss.bitrise.io/u/jarryd)\
**Post date:** [July 17, 2017, 1:53pm UTC](https://discuss.bitrise.io/t/generate-a-url-for-fastlane-snapshot-html-output/2284/1 "2017-07-17T13:53:27Z")

</div>

Fastlane’s snapshot generates an html file with all the screenshots grouped for each device tested. It would be great if bitrise could generate a url for the build so that the output html file can be viewed. Possibly just one url per branch running this so that there is no wasted disk usage for old builds, snapshot replaces screenshots if user sets that.

The use case for this is purely for better visibility of the output of a snapshot run for a branch or pull-request. If non-technical users are reviewing the results, it would be nice if the UX supports this.

---

<div class="post-metadata">

**Author:** ![viktorbenei](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/viktorbenei/32/18_2.png) [@viktorbenei](https://discuss.bitrise.io/u/viktorbenei)\
**Post date:** [July 17, 2017, 1:55pm UTC](https://discuss.bitrise.io/t/generate-a-url-for-fastlane-snapshot-html-output/2284/2 "2017-07-17T13:55:37Z")

</div>

Already possible with the **Deploy to [Bitrise.io](http://Bitrise.io)** step. Please see: [Screenshot.html from Fastlane Snapshot](http://discuss.bitrise.io/t/screenshot-html-from-fastlane-snapshot/1124)

---

<div class="post-metadata">

**Author:** ![viktorbenei](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/viktorbenei/32/18_2.png) [@viktorbenei](https://discuss.bitrise.io/u/viktorbenei)\
**Post date:** [July 17, 2017, 1:56pm UTC](https://discuss.bitrise.io/t/generate-a-url-for-fastlane-snapshot-html-output/2284/3 "2017-07-17T13:56:59Z")

</div>

If that wouldn’t be enough, to view more complex HTML artifacts directly on the build’s page, please vote & comment here:

> [@Artifacts: Make it possible to view HTML files with relative links (CSS etc. refs)](http://discuss.bitrise.io/t/artifacts-make-it-possible-to-view-html-files-with-relative-links-css-etc-refs/145):
>
> From @viktorbenei on Sat Dec 10 2016 10:29:41 GMT-0500 (EST) Right now artifacts are exposed with special, pre-signed, time limited URLs. This means that the exact download / access link for an artifact is generated and does change every time it’s accessed. This makes relative links between artifacts unusable when viewed directly on the web UI. This issue mainly affects HTML files/reports, where the HTML file references other resources (like CSS, JavaScript, etc. files) with relative links. F…

---

<div class="post-metadata">

**Author:** ![viktorbenei](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/viktorbenei/32/18_2.png) [@viktorbenei](https://discuss.bitrise.io/u/viktorbenei)\
**Post date:** [July 20, 2017, 1:57pm UTC](https://discuss.bitrise.io/t/generate-a-url-for-fastlane-snapshot-html-output/2284/4 "2017-07-20T13:57:07Z")

</div>

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.
