---
title: "Discussion on \"How We Built a Progressive Proxy Upload Architecture for Multi‑GB PSD & RAW Files\" | Hashnode"
description: "Discussion on \"How We Built a Progressive Proxy Upload Architecture for Multi‑GB PSD & RAW Files\". How we made 30 GB PSD uploads feel instant without expensive backend conversions.\n\nWhen we first built our media upload system, the architecture looked completely normal. A user uploaded a file, the b"
url: "https://hashnode.com/posts/how-we-built-a-progressive-proxy-upload-architecture-for-multi-gb-psd-raw-files/6a10aa5c1f237623ea284da8"
---

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

Discussion

# [How We Built a Progressive Proxy Upload Architecture for Multi‑GB PSD & RAW Files](https://blog.nishikanta.in/how-we-built-a-progressive-proxy-upload-architecture-for-multi-gb-psd-raw-files?utm_source=hashnode&utm_medium=feed)

How we made 30 GB PSD uploads feel instant without expensive backend conversions. When we first built our media upload system, the architecture looked completely normal. A user uploaded a file, the b

May 22 · 6 min read · blog.nishikanta.in  
Read the article

-   [#architecture-design](https://hashnode.com/tag/architecture-design)
-   [#system-design](https://hashnode.com/tag/system-design)
-   [#backend](https://hashnode.com/tag/backend)

## Written by

[Nishikanta Ray](https://hashnode.com/@nishikanta236)

@nishikanta236 · India

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

Fullstack Developer

## Responses 1

Markdown supported · ⌘↵ to post

[Node Edge Ops](https://hashnode.com/@nodeedgeops)

[Nov 4](https://hashnode.com/posts/how-we-built-a-progressive-proxy-upload-architecture-for-multi-gb-psd-raw-files/6a10aa5c1f237623ea284da8/comment/6aeba140275626370acefabd)

Large uploads through nginx into a Node handler fail in predictable ways when buffering defaults stay on. For multi-GB bodies I set client\_max\_body\_size high enough on that location only, turn proxy\_request\_buffering off so nginx streams to upstream instead of spooling disk, and raise proxy\_read\_timeout / proxy\_send\_timeout well above the slowest legitimate upload. Leaving buffering on looks like random 413/504 under load even when the Node process is healthy.

Ops check after enabling: upload a multi-hundred-MB file through the public path and watch whether nginx workers spike disk I/O (still buffering) versus steady upstream sockets. Keep a separate stricter limit on non-upload API locations so one raised body size does not become an abuse path. If you terminate TLS at the edge, confirm the Node app sees Content-Length or chunked framing unchanged — middleware that re-buffers the whole body in memory will OOM long before nginx complains.
