Deploy and Host Reframe on Railway

Reframe is a free, open-source video editor that runs entirely in the browser using WebAssembly and FFmpeg. Users can resize, trim, rotate, convert, and export videos without creating an account or uploading files to a server. Built with Next.js and TypeScript, Reframe delivers a fast, privacy-first editing experience while keeping all media processing on the user's device.

About Hosting Reframe

Hosting Reframe on Railway provides a simple way to deploy the application's static frontend without managing infrastructure manually. Railway automatically builds the Next.js project, serves the generated static assets over HTTPS, and provides public networking through a custom Railway domain. Since Reframe performs all video processing locally in the browser using FFmpeg WebAssembly, no server-side rendering, background workers, databases, or persistent storage are required for normal operation. Railway also streamlines deployments through Git-based workflows, making it easy to publish updates while providing reliable global hosting and automatic HTTPS for end users.

Common Use Cases

Browser-based video resizing and conversion
Privacy-focused online video editing
Self-hosted video editing tools for creators and organizations

Dependencies for Reframe Hosting

Modern browser with WebAssembly (WASM) support
FFmpeg WebAssembly (ffmpeg.wasm)

Deployment Dependencies

Resource	URL
GitHub Repository	https://github.com/magic-peach/reframe
Next.js Documentation	https://nextjs.org/docs
FFmpeg.wasm Documentation	https://ffmpegwasm.netlify.app/docs/overview
React Documentation	https://react.dev
Tailwind CSS Documentation	https://tailwindcss.com/docs

Implementation Details

Docker

No Docker image or Dockerfile is documented.

Railway automatically builds the Next.js application from the repository during deployment.

Public Networking

Configure the Railway service with an HTTP proxy.

Setting	Value
Proxy Type	HTTP Proxy
Target Port	8080

Environment Variables

No runtime environment variables are documented for production deployment.

Variable	Required	Description
None	—	Reframe does not require any documented environment variables for standard deployments.

Raw Editor example:

# No runtime environment variables are required.

HTTP Security Headers

Reframe uses FFmpeg WebAssembly, which requires SharedArrayBuffer support. To enable this in modern browsers, configure the following response headers for your Railway deployment:

Header	Value
`Cross-Origin-Opener-Policy`	`same-origin`
`Cross-Origin-Embedder-Policy`	`require-corp`

These headers are required for FFmpeg WebAssembly to function correctly in browsers that enforce cross-origin isolation.

Persistent Storage

A Railway Volume is not required.

Reframe processes videos entirely within the user's browser. Uploaded files are never stored on the Railway instance, and exported videos are downloaded directly to the user's device.

Database

No database service is required.

The application does not depend on PostgreSQL, MySQL, MongoDB, Redis, or any other server-side database.

Build & Start

Railway automatically builds the Next.js application from the repository.

No custom build or start commands are required.

Accessing the Application

After deployment:

Open your Railway project.
Navigate to Settings → Networking.
Generate a Railway domain.
Open the generated HTTPS URL in a modern browser.

No user accounts, authentication, or administrator setup are required before using the application.

Why Deploy Reframe on Railway?

Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.

By deploying Reframe on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.