---
title: "Comment by Mark Reeves on \"Building image & video conversion that never leaves the browser\" | Hashnode"
description: "heic plus compression plus video transcoding with no server is a serious trio - video is usually where client-side stories fall apart on memory. how are you han"
url: "https://hashnode.com/posts/building-image-video-conversion-that-never-leaves-the-browser/6a851c20063e7f19e4c31659/comment/6abac2e0ec8d84c400c26d54"
---

[Discussion](https://hashnode.com/posts/building-image-video-conversion-that-never-leaves-the-browser/6a851c20063e7f19e4c31659)

Comment [Building image & video conversion that never leaves the browser](https://hashnode.com/posts/building-image-video-conversion-that-never-leaves-the-browser/6a851c20063e7f19e4c31659)

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

[Sep 28](https://hashnode.com/posts/building-image-video-conversion-that-never-leaves-the-browser/6a851c20063e7f19e4c31659/comment/6abac2e0ec8d84c400c26d54)

heic plus compression plus video transcoding with no server is a serious trio - video is usually where client-side stories fall apart on memory. how are you handling the transcode step for larger files, chunked processing or does it all sit in memory?
