# Let's make HandleURL file download better!

**URL:** <https://forum.xojo.com/t/lets-make-handleurl-file-download-better/79740>\
**Category:** Web\
**Created:** [March 26, 2024, 10:53pm UTC](https://forum.xojo.com/t/lets-make-handleurl-file-download-better/79740 "2024-03-26T22:53:05Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Georgios\_Poulopoulos](https://forum.xojo.com/user_avatar/forum.xojo.com/georgios_poulopoulos/32/16905_2.png) [@Georgios\_Poulopoulos](https://forum.xojo.com/u/Georgios_Poulopoulos)\
**Post date:** [March 26, 2024, 10:53pm UTC](https://forum.xojo.com/t/lets-make-handleurl-file-download-better/79740/1 "2024-03-26T22:53:05Z")

</div>

First of all, congratulations on the 2024R1 release!  
I noticed the improvement in memory clean-up after a download: takes about a minute VS much more in previous versions.

But as things still hold, when downloading a file, the entirety of its contents are loaded into memory. For small files it goes unnoticed, for bigger files, it really shows.

**I’ve been thinking…would it be a huge refactor in that part of the framework if the download was somewhat chunked and didn’t require all that memory when in progress?**

I have to say I tried implementing something like that in [this -unrelated to Web2- project](https://github.com/gregorplop/fswebapi), but blew up in my face for reasons I have no way of investigating.

Xojo engineers: Would it be something you could look into?  
Xojo users: Would you consider this a meaningful enhancement?

Thanks!