---
title: "Discussion on \"How We Built a Fast Browser-Based Video Tool\" | Hashnode"
description: "Discussion on \"How We Built a Fast Browser-Based Video Tool\". A developer write-up on how we built Animation Maker"
url: "https://hashnode.com/posts/how-we-built-a-fast-browser-based-video-tool/6a8d67bde48cd39ade1943d0"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [How We Built a Fast Browser-Based Video Tool](https://mehmetabak.hashnode.dev/how-we-built-a-fast-browser-based-video-tool?utm_source=hashnode&utm_medium=feed)

A developer write-up on how we built Animation Maker

Aug 25 · 6 min read · mehmetabak.hashnode.dev  
Read the article

-   [#web-development](https://hashnode.com/tag/web-development)
-   [#coding](https://hashnode.com/tag/coding)
-   [#developer](https://hashnode.com/tag/developer)
-   [#animation](https://hashnode.com/tag/animation)

## Written by

[Mehmet Abak](https://hashnode.com/@mehmetabak)

@mehmetabak

  
[View profile](https://hashnode.com/@mehmetabak)

A Software Developer

A Software Developer

## Responses 1

Markdown supported · ⌘↵ to post

[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.
