Privacy-First Video Converter Integration

I’m extending my existing Node.js (API layer) and Next.js (frontend) website with a compact, privacy-first media converter. Your task is to wire a server-side FFMPEG (or equally efficient) pipeline into the current codebase and surface it through a page that feels native to our brand.

Core requirements
• Conversions: MOV → MP4, WEBM → MP4, MP4 → MOV, MP4 → MP3 only—no other formats need support.
• No accounts, no history, no long-term storage. Uploaded files must auto-purge as soon as the download finishes or, at most, 5–10 minutes later.
• Size caps: 200 MB for video, 100 MB for audio, enforced both client and server side.
• UI: a drag-and-drop zone styled to match the site’s existing color palette, typography, and button styles.
• Robust error handling for oversize files, unsupported formats, and conversion failures.

Deliverables
1. Fully integrated converter route(s) in our Node/Next repository, ready for production deploy.
2. Clean React component(s) that plug into our layout and show real-time conversion status (simple progress bar or spinner—whichever is lighter to implement without bloat).
3. Configuration notes and a brief README covering environment variables, temporary-file location, and Cloud/VM resources required so we stay within budget.
4. A short test script or instructions to verify that files never persist beyond the permitted window.

If you can keep the code lean, secure, and easy to maintain, let’s get started right away.