---
title: "Comment by Mark Reeves on \"How We Built a Fast Browser-Based Video Tool\" | Hashnode"
description: "fast browser-based video is where most web tools fall over - the render step eats memory and the tab dies on longer clips. how did you keep it fast, canvas comp"
url: "https://hashnode.com/posts/how-we-built-a-fast-browser-based-video-tool/6a8d67bde48cd39ade1943d0/comment/6abb88a46a1180331363480e"
---

[Discussion](https://hashnode.com/posts/how-we-built-a-fast-browser-based-video-tool/6a8d67bde48cd39ade1943d0)

Comment [How We Built a Fast Browser-Based Video Tool](https://hashnode.com/posts/how-we-built-a-fast-browser-based-video-tool/6a8d67bde48cd39ade1943d0)

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

[Sep 29](https://hashnode.com/posts/how-we-built-a-fast-browser-based-video-tool/6a8d67bde48cd39ade1943d0/comment/6abb88a46a1180331363480e)

fast browser-based video is where most web tools fall over - the render step eats memory and the tab dies on longer clips. how did you keep it fast, canvas compositing or webcodecs? curious what the bottleneck turned out to be.
