# Making p5.js downloadable again (solved)

**URL:** <https://discourse.processing.org/t/making-p5-js-downloadable-again-solved/13457>\
**Category:** p5.js\
**Created:** [August 18, 2019, 8:04pm UTC](https://discourse.processing.org/t/making-p5-js-downloadable-again-solved/13457 "2019-08-18T20:04:01Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![EnderArchery](https://avatars.discourse-cdn.com/v4/letter/e/e47774/32.png) [@EnderArchery](https://discourse.processing.org/u/EnderArchery)\
**Post date:** [August 18, 2019, 8:04pm UTC](https://discourse.processing.org/t/making-p5-js-downloadable-again-solved/13457/1 "2019-08-18T20:04:01Z")

</div>

Well, as you might have noticed, every download link on the [p5js.org](http://p5js.org) page takes you to their support page.  
And that’s it unfortunately. You apparently can’t download it.

---

<div class="post-metadata">

**Author:** ![EnderArchery](https://avatars.discourse-cdn.com/v4/letter/e/e47774/32.png) [@EnderArchery](https://discourse.processing.org/u/EnderArchery)\
**Post date:** [August 18, 2019, 8:06pm UTC](https://discourse.processing.org/t/making-p5-js-downloadable-again-solved/13457/2 "2019-08-18T20:06:26Z")

</div>

I’ve just noticed, that you can download it by opening the links in a new tab.  
Ahm… am I the only one experiencing these weird issues?

---

<div class="post-metadata">

**Author:** ![Tiemen](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.processing.org/tiemen/32/5477_2.png) [@Tiemen](https://discourse.processing.org/u/Tiemen)\
**Post date:** [August 18, 2019, 10:23pm UTC](https://discourse.processing.org/t/making-p5-js-downloadable-again-solved/13457/3 "2019-08-18T22:23:01Z")

</div>

Not sure whether we’re talking about the same links, but when I press the big, red coloured link ‘download’ on [https://p5js.org/](https://p5js.org/) I get redirected to the download page. When I thereafter press on ‘p5.js complete’ I get redirected to their support page, but a pop-up appears asking whether I want to save or open _p5.zip_.

I used the latest version of Firefox and everything seems to be a-ok; perhaps some browser or pc setting issue?

---

<div class="post-metadata">

**Author:** ![outofambit](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.processing.org/outofambit/32/24_2.png) [@outofambit](https://discourse.processing.org/u/outofambit)\
**Post date:** [August 19, 2019, 3:38am UTC](https://discourse.processing.org/t/making-p5-js-downloadable-again-solved/13457/4 "2019-08-19T03:38:38Z")

</div>

hey @EnderArchery! i saw [this bug](https://github.com/processing/p5.js-website/issues/484) in the p5 website repository and i think it might be what you are experiencing? does downloading work if you disable your pop up blocker?

---

<div class="post-metadata">

**Author:** ![EnderArchery](https://avatars.discourse-cdn.com/v4/letter/e/e47774/32.png) [@EnderArchery](https://discourse.processing.org/u/EnderArchery)\
**Post date:** [August 19, 2019, 7:18am UTC](https://discourse.processing.org/t/making-p5-js-downloadable-again-solved/13457/5 "2019-08-19T07:18:27Z")

</div>

Well, I tried disabling my Ad-Blockers, but Chrome has a pup-up blocker itself. And it doesn’t even try to alert me, that there was an incident. I thought about the same when I noticed that opening the link in a new tab works.  
Disabling the built in blocker resolved my problems.

But I still think there should be downloadlinks on the support page, when you access it from the download section. 🤷‍♂️

---

<div class="post-metadata">

**Author:** ![jeremydouglass](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.processing.org/jeremydouglass/32/20_2.png) [@jeremydouglass](https://discourse.processing.org/u/jeremydouglass)\
**Post date:** [August 19, 2019, 3:27pm UTC](https://discourse.processing.org/t/making-p5-js-downloadable-again-solved/13457/6 "2019-08-19T15:27:41Z")

</div>

@EnderArchery – maybe comment on the issue and give your Chrome version number and what OS you are on?

> <https://github.com/processing/p5.js-website/issues/484>

Always good for devs to have direct contact with a person who is actually experiencing the problem.