If you're looking to use tools like FFmpeg alongside your n8n workflows on Railway, you'll need to customize the deployment environment. By default, the official n8n Docker image doesn’t include additional utilities like FFmpeg, but with a custom Dockerfile, it's straightforward to add them and deploy a fully integrated solution.

To get started, create a Dockerfile that extends the official n8n image and installs FFmpeg using standard Debian package management. Here's an example:

FROM n8nio/n8n:1.93.0 # Install ffmpeg and other optional tools USER root RUN apt-get update && apt-get install -y \ ffmpeg \ curl \ wget \ && apt-get clean \ && rm -rf /var/lib/apt/lists/* # Switch back to n8n user to maintain security best practices USER node

This configuration ensures that the n8n environment stays intact while enabling access to powerful tools like FFmpeg. After creating the Dockerfile, push it to a GitHub repository and connect that repo to a new service in Railway. Railway will detect the Dockerfile and automatically build and deploy your customized container.

Don't forget to configure your environment variables in Railway as well. At a minimum, you should set:

• N8N_ENCRYPTION_KEY: a persistent encryption key to retain credentials across redeploys

• DATABASE_URL: a connection string to a persistent PostgreSQL database

• Any other N8N_ configuration variables required for your workflows

Once deployed, FFmpeg will be available within your container. You can use it in n8n workflows via the Execute Command node or custom scripts.

By combining FFmpeg and n8n in a single Railway deployment, you unlock a range of possibilities—like video/audio processing, automation with media files, or advanced integrations. This method gives you full control over your environment without sacrificing the simplicity and scalability Railway offers.