---
title: "Comment by Mark Reeves on \"How Client-Side Processing Changes Image Conversion\" | Hashnode"
description: "upload first process second was the default for so long that users stopped noticing the upload at all. we built swapfile.live around the flipped model - browser"
url: "https://hashnode.com/posts/how-client-side-processing-changes-image-conversion/6a7bdcdecc9b4a884fe285b2/comment/6abab69cfe42382088aa46c0"
---

[Discussion](https://hashnode.com/posts/how-client-side-processing-changes-image-conversion/6a7bdcdecc9b4a884fe285b2)

Comment [How Client-Side Processing Changes Image Conversion](https://hashnode.com/posts/how-client-side-processing-changes-image-conversion/6a7bdcdecc9b4a884fe285b2)

[Mark Reeves](https://hashnode.com/@mreevestools)

[Sep 28](https://hashnode.com/posts/how-client-side-processing-changes-image-conversion/6a7bdcdecc9b4a884fe285b2/comment/6abab69cfe42382088aa46c0)

upload first process second was the default for so long that users stopped noticing the upload at all. we built swapfile.live around the flipped model - browser does the work, nothing leaves the tab. the trust difference shows up the first time someone converts something sensitive. great breakdown of the shift
