Skip to main content

Contrib Packages

· 4 min read
Fiber Team
Fiber Team
Maintainers

Fiber's core ships with 20+ middleware - logger, CORS, rate limiter, sessions, and more. But some middleware needs external dependencies: JWT requires a token library, OpenTelemetry needs the OTel SDK, WebSockets depend on a WebSocket implementation. Instead of bloating Fiber's core with these dependencies, they live in a separate repository: gofiber/contrib.

The contrib packages are first-party middleware. Same team, same quality, same release cycle. The only difference is that they have external Go dependencies, so they are imported separately to keep your go.sum clean when you do not need them.

What is in Contrib​

The contrib repository contains 18+ middleware packages. Here are the ones you will reach for most often:

JWT Authentication​

The most popular contrib package. It validates JSON Web Tokens and protects routes:

import jwtware "github.com/gofiber/contrib/v3/jwt"

app.Use(jwtware.New(jwtware.Config{
    SigningKey: jwtware.SigningKey{Key: []byte("your-secret-key")},
}))

app.Get("/protected", func(c fiber.Ctx) error {
    user := c.Locals("user").(*jwt.Token)
    claims := user.Claims.(jwt.MapClaims)
    return c.JSON(fiber.Map{"user": claims["sub"]})
})

The middleware extracts the token from the Authorization: Bearer <token> header, validates it, and stores the parsed token in c.Locals("user"). Invalid or missing tokens return 401 automatically.

WebSocket​

Real-time communication with WebSocket support:

import "github.com/gofiber/contrib/v3/websocket"

app.Get("/ws", websocket.New(func(c *websocket.Conn) {
    for {
        mt, msg, err := c.ReadMessage()
        if err != nil {
            break
        }
        // Echo the message back
        c.WriteMessage(mt, msg)
    }
}))

The WebSocket middleware upgrades HTTP connections to WebSocket and gives you a connection object with ReadMessage / WriteMessage for bidirectional communication.

OpenTelemetry (otelfiber)​

Distributed tracing and metrics for your Fiber app:

import "github.com/gofiber/contrib/otelfiber/v2"

app.Use(otelfiber.Middleware())

One line. Every request gets a trace span with method, route, status code, and duration. The spans flow into whatever OpenTelemetry collector you have configured - Jaeger, Zipkin, Datadog, Grafana Tempo.

Swagger​

Auto-serve your Swagger/OpenAPI documentation:

import "github.com/gofiber/contrib/v3/swagger"

app.Use(swagger.New(swagger.Config{
    BasePath: "/api/",
    FilePath: "./docs/swagger.json",
    Path:     "docs",
}))

This serves the Swagger UI at /docs with your API specification. Generate the spec with tools like swag or write it manually.

Socket.io​

Full Socket.io server implementation for real-time event-based communication:

import "github.com/gofiber/contrib/v3/socketio"

socketio.On(socketio.EventMessage, func(ep *socketio.EventPayload) {
    ep.Kws.Emit([]byte("Hello back!"), socketio.TextMessage)
})

app.Get("/ws/:id", socketio.New(func(kws *socketio.Websocket) {}))

Circuit Breaker​

Protect your app from cascading failures when upstream services are down:

import "github.com/gofiber/contrib/v3/circuitbreaker"

app.Use(circuitbreaker.New(circuitbreaker.Config{
    Timeout:          5 * time.Second,
    MaxRequests:      3,
    Interval:         30 * time.Second,
    ReadyToTrip: func(counts circuitbreaker.Counts) bool {
        return counts.ConsecutiveFailures > 5
    },
}))

Load Shedding​

Reject excess traffic before it overwhelms your service:

import "github.com/gofiber/contrib/v3/loadshed"

app.Use(loadshed.New(loadshed.Config{
    MaxConcurrent: 100,
}))

When your service is at capacity, new requests get 503 instead of making everything slow.

More Contrib Packages​

PackagePurpose
fiberzapStructured logging with Uber's Zap
fiberzerologStructured logging with zerolog
fibersentryError tracking with Sentry
fibernewrelicAPM with New Relic
fiberi18nInternationalization support
opafiberPolicy enforcement with Open Policy Agent
pasetoPASETO token authentication (alternative to JWT)
hcaptchahCaptcha verification
casbinAuthorization with Casbin
fgprofFull goroutine profiling
monitorReal-time server metrics dashboard

Core vs. Contrib: How to Decide​

  • If it has no external Go dependencies → it is in core (github.com/gofiber/fiber/v3/middleware/...)
  • If it requires external libraries → it is in contrib (github.com/gofiber/contrib/...)

This split keeps your binary small. If you build an API that does not use JWT, you do not pull in the JWT library and its transitive dependencies.

v3 Support​

For Fiber v3, the contrib packages use a dedicated v3 base path. All v3-compatible imports start with github.com/gofiber/contrib/v3/:

// Fiber v3 import path
import jwtware "github.com/gofiber/contrib/v3/jwt"
import "github.com/gofiber/contrib/v3/websocket"
import "github.com/gofiber/contrib/v3/otelfiber"

The documentation shows the v3_ prefix in versioning to indicate Fiber v3 compatibility. Check each package's documentation page for the exact import path.

Internal References​