Building a Robust FFmpeg Video Transcoding Pipeline

Users upload videos in all sorts of formats—MOV from iPhones, MKV from torrents, AVI from 2008. The backend must accept them and serve a browser-friendly MP4/H.264 or WebM/VP9 without blocking the web process for minutes of transcoding. We designed a fault-tolerant pipeline that has been used in production for years—implemented it for over 30 projects. The result: adaptive quality profiles, real-time progress, and ready notifications. Typical server resource savings reach 40%—for a $1000 monthly server, that's $400 saved. CDN traffic costs drop significantly.

Why should you use asynchronous transcoding?

Video transcoding is a CPU-intensive operation that can take from seconds to tens of minutes depending on the clip length and encoding profile. Synchronous processing within an HTTP request is out of the question: it would block the web worker, cause timeouts, and tank responsiveness. The correct approach is an asynchronous job queue. Hardware encoding (NVENC) processes video 3x faster than software, but even it should not block the request.

Building a Transcoding Pipeline

The architecture includes several components. Below is a step-by-step process:

1. Upload: the file is saved to object storage or local disk; a job ID is returned.
2. Queue: a Job is pushed into a queue (RabbitMQ, Redis, SQS) to avoid blocking the HTTP request. This queue job video processing model ensures decoupling.
3. Worker: picks up the Job, runs FFmpeg with the required parameters, writes progress to Redis.
4. Notification: after completion, updates the database and notifies the client via WebSocket or polling.

A typical set of adaptive profiles for bitrate ladder:

CRF (Constant Rate Factor) is the primary quality parameter for H.264 (H.264 conversion is handled by libx264): 18 = near lossless, 28 = acceptable quality at small size. preset affects encoding speed vs. file size. We use a Laravel FFmpeg service class to manage these profiles.

For HLS compatibility, we set keyframe interval (GOP size) to 2 seconds (e.g., -g 48 for 24fps). Using b-pyramid can improve compression by 5-10%. VMAF (Video Multimethod Assessment Fusion) metrics help fine-tune bitrate allocation per profile.

Tracking Transcoding Progress

FFmpeg can output progress via pipe. The worker parses lines in the format out_time_usec=... and saves percentages in Redis. The client receives updates via WebSocket (e.g., Laravel Echo) or polling. This allows accurate progress display without delays. Asynchronous video processing prevents timeouts. The progress mechanism is described in the FFmpeg documentation.

Container choice depends on the task: MP4 is universal for streaming, WebM with VP9 gives better compression, MKV is suitable for archival storage with subtitles. For the web, we recommend MP4 with H.264—browsers don't require plugins.

Implementing an FFmpeg Service

The key element is a service that manages the FFmpeg process with progress handling. This video processing PHP library handles the transcoding:

namespace App\Services;

class FfmpegService
{
    public function transcode(
        string $inputPath,
        string $outputPath,
        array  $profile,
        ?callable $onProgress = null
    ): void {
        $width   = $profile['width'];
        $height  = $profile['height'];
        $videoBr = $profile['video_br'];
        $audioBr = $profile['audio_br'];
        $preset  = $profile['preset'];
        $crf     = $profile['crf'];

        // scale with aspect ratio preservation, pad to target size
        $scaleFilter = "scale={$width}:{$height}:force_original_aspect_ratio=decrease,"
            . "pad={$width}:{$height}:(ow-iw)/2:(oh-ih)/2:black";

        $cmd = implode(' ', [
            'ffmpeg -y',
            "-i " . escapeshellarg($inputPath),
            "-vf " . escapeshellarg($scaleFilter),
            "-c:v libx264",
            "-preset {$preset}",
            "-crf {$crf}",
            "-maxrate {$videoBr}",
            "-bufsize " . (intval($videoBr) * 2) . "k",
            "-c:a aac",
            "-b:a {$audioBr}",
            "-movflags +faststart",
            "-progress pipe:1",
            "-loglevel error",
            escapeshellarg($outputPath),
        ]);

        $descriptors = [
            0 => ['pipe', 'r'],
            1 => ['pipe', 'w'],
            2 => ['pipe', 'w'],
        ];

        $proc = proc_open($cmd, $descriptors, $pipes);
        // ... read progress and check exit code
    }
}

-movflags +faststart is mandatory: it moves the moov atom to the beginning of the MP4, allowing the browser to start playback before fully downloading the file. Without it, the video won't start until the entire file is downloaded.

Choosing Between Software and Hardware Encoding

Software encoding (libx264) delivers better quality at low bitrates but is slower. Hardware encoding (NVENC) is faster but may degrade quality under strong compression. Comparison:

For production, we often combine: NVENC hardware acceleration for previews, libx264 for final archive. The optimal choice depends on your priorities: speed or quality. Advanced rate-distortion optimization (RDO) in libx264 further improves compression efficiency, albeit at higher computational cost.

What's Included in the Work

As part of developing this FFmpeg pipeline, we provide:

• Queue setup (RabbitMQ/Redis) and supervisor worker for workers.
• Implementation of an FFmpeg service with progress parsing.
• Creation of Job classes with success/error handlers.
• Configuration of adaptive profiles for your needs.
• Endpoints to retrieve progress and results.
• WebSocket notification integration (optional).
• Deployment and monitoring documentation.
• Post-delivery support and training.

The pipeline development typically costs between $800 and $1200 and delivers a return on investment within a few months through reduced server and CDN costs.

Timeline and Ordering

Developing a basic pipeline takes 2 to 4 days, depending on profile complexity and WebSocket requirements. We'll evaluate your project for free—contact us to discuss the details. We guarantee code quality and post-delivery support.

Use these recommendations—and your pipeline will run stably even under high load.

Backend Development Services: Laravel, Node.js, Go, Django, PostgreSQL

On a production server at 3:14 AM, the Laravel Jobs queue stopped processing. 40,000 unprocessed jobs in Redis. Cause: worker crashed due to a memory leak in one of the Jobs (leak via a static variable in an Eloquent observer), supervisor didn't restart it because of misconfigured stopwaitsecs. This is not a hypothetical scenario — it's Tuesday. We analyzed such an incident on a project with 500 RPS load: diagnosis took 4 hours, fix — 20 minutes. So you don't lose money on downtime, we offer backend development services with a focus on production-grade reliability. We'll assess your project in 2 days.

Backend is what works when no one is watching. Or doesn't work. We guarantee you'll have the first option.

How do we ensure production-grade reliability from day one?

What we do correctly from day one

Service Layer over Fat Controllers. Controller receives HTTP request, validates it via Form Request, passes data to Service, returns response. Business logic in Service, not Controller. This sounds trivial, but most legacy projects have controllers with 500 lines and SQL queries inside.

Repository Pattern we use cautiously. If you just wrap Model::where(...) in a repository method — that's boilerplate without benefit. Repository is justified when: you need to abstract from the data source (DB + cache + external API) or when query logic is complex enough to isolate.

Jobs, Events, Listeners. Everything that can be async — make async. Sending email, PDF generation, external API sync, aggregate recalculation — into Queue. Laravel Horizon for queue monitoring in Redis: see throughput, failed jobs, processing time per queue.

How Octane handles high load

Laravel Octane with RoadRunner or Swoole keeps the app in memory between requests — removes bootstrap overhead (config loading, class autoloading) on each HTTP request. Gain: 3–8x on synthetic benchmarks, 2–4x on real applications. Important: no state between requests in static variables — that leads to exactly the incidents from the beginning. We use this in projects with >1000 RPS.

What to do about N+1 queries

N+1 is the most common cause of slow pages in Laravel apps. Standard story: page worked fine on dev with 10 records, on production with 10,000 — 8-second load.

Laravel Debugbar in dev environment shows the number of queries per page. More than 20 queries per page — signal for audit.

Model::preventLazyLoading(! app()->isProduction());

Telescope for profiling in staging: logs all queries, jobs, mail, notifications with time detail. Numbers: after implementing eager loading, page load time drops from 8s to 0.3s — 27 times faster.

PostgreSQL: indexes that are actually needed

PostgreSQL 14+ is the primary DB on all projects. We use PgBouncer + PostgreSQL combination. 10+ years experience, more than 50 backend projects, 5 years on the market.

How PostgreSQL helps avoid slow queries

Composite indexes for frequent WHERE + ORDER BY. If you have WHERE user_id = ? AND status = ? ORDER BY created_at DESC — you need (user_id, status, created_at DESC). A separate index on (user_id) doesn't help much with sorting.

Partial indexes. If 95% of queries go with WHERE status = 'active':

CREATE INDEX idx_orders_active ON orders (created_at DESC)
WHERE status = 'active';

The index is small, fast, covers the main load.

GIN indexes for JSONB and arrays. @> operator without GIN index — seq scan. With index — fast even on millions of rows.

GIN for full-text search. to_tsvector + GIN instead of LIKE '%query%'. LIKE without index is always seq scan. With pg_trgm extension and gin_trgm_ops — supports LIKE with index, useful for CRM search by partial match.

Connection pooling: why it's more important than it seems

Rails, Laravel, Django open a new connection to PostgreSQL for each PHP/Python process. With 100 workers — 100 connections. PostgreSQL starts degrading from 200–300 active connections — overhead on connection management becomes significant.

PgBouncer — connection pooler in front of PostgreSQL. Transaction pooling mode: connection to PostgreSQL is occupied only during a transaction, returned to pool between requests. 1000 application workers → 20–50 actual connections to PostgreSQL. This reduces latency by 40% and hosting costs by 30%.

Node.js with Fastify: when it's better than Laravel

Node.js is justified for:

• Realtime: WebSocket servers, Server-Sent Events, chat, live updates
• Streaming: large files, video, streaming data
• High I/O concurrency: many parallel requests to external APIs without heavy business logic
• Serverless: Lambda/Cloud Functions — Node.js starts faster than PHP

Fastify over Express: 2–3 times faster on benchmarks, built-in JSON Schema validation, better TypeScript support, plugin architecture.

Typical realtime architecture: Laravel — core business logic and REST API. Node.js + Socket.io or ws — WebSocket server. Laravel publishes events to Redis Pub/Sub, Node.js subscribes and broadcasts to clients. This separation allows scaling the WebSocket server independently of the main app.

Go: microservices and high load

Go we use for:

• High-load microservices (>10,000 RPS)
• Background workers with strict latency requirements
• DevOps tools and CLI
• gRPC services in microservice architecture

Goroutines — thousands of times cheaper than OS threads. 10,000 concurrent connections on Go is normal on one server.

But Go is not a silver bullet. Development is slower than Laravel: more boilerplate, no ORM at Eloquent level, error handling with if err != nil everywhere. Justified only when performance is a real requirement, not an assumption.

Django and Python backend

Django with DRF (Django REST Framework) — for tasks where Python is needed: ML pipelines, data processing, integrations with AI tools.

Celery for background tasks — similar to Laravel Queue but more complex to configure. Celery Beat for cron tasks.

Django ORM vs raw SQL: ORM is convenient for CRUD. For analytical queries with multiple JOINs, window functions, and CTEs — connection.execute() with raw SQL is more readable and predictable.

Redis: not just cache

Redis in our projects plays multiple roles:

Redis Cluster for horizontal scaling. Sentinel for automatic failover on standalone setups.

Deployment and infrastructure

Docker + docker-compose — standard for local development and production. Each service in a container: PHP-FPM/Octane, Nginx, PostgreSQL, Redis, Queue Worker, Scheduler.

CI/CD via GitHub Actions:

1. Run tests (PHPUnit / Pest, Vitest, Playwright)
2. Build Docker image
3. Push to Container Registry
4. Deploy: docker pull → docker-compose up -d on server, or Kubernetes rolling update

Zero-downtime deploy for Laravel: php artisan down --secret=TOKEN is not needed with proper configuration. Strategy: new container starts next to the old one, Nginx switches traffic after health check, old container stops.

Monitoring: Sentry for exception tracking with alerting in Slack/Telegram. Grafana + Prometheus (or Grafana Cloud) for metrics: CPU, memory, request rate, queue depth, database connection count. Alerts on: error rate > 1%, p99 latency > 2s, queue depth > 1000 jobs.

What's included in turnkey work

• Architecture design (API documentation, DB schema, service diagram)
• Implementation according to agreed specification with code review
• CI/CD, monitoring, alerting setup
• Load testing (k6, wrk) with report
• Handover of source code, access, deployment instructions
• Training of customer's team (2-3 sessions)
• Warranty support for 1 month after delivery

Timeline benchmarks

Pricing is calculated individually after analyzing load, integrations, and business logic. Contact us for a free audit of your current backend — get an optimization plan in 2 days. Request a consultation.