Skip to main content
Version: Next


How should I structure my application?

There is no definitive answer to this question. The answer depends on the scale of your application and the team that is involved. To be as flexible as possible, Fiber makes no assumptions in terms of structure.

Routes and other application-specific logic can live in as many files as you wish, in any directory structure you prefer. View the following examples for inspiration:

How do I handle custom 404 responses?

If you're using v2.32.0 or later, all you need to do is to implement a custom error handler. See below, or see a more detailed explanation at Error Handling.

If you're using v2.31.0 or earlier, the error handler will not capture 404 errors. Instead, you need to add a middleware function at the very bottom of the stack (below all other functions) to handle a 404 response:

app.Use(func(c fiber.Ctx) error {
return c.Status(fiber.StatusNotFound).SendString("Sorry can't find that!")

How can i use live reload ?

Air is a handy tool that automatically restarts your Go applications whenever the source code changes, making your development process faster and more efficient.

To use Air in a Fiber project, follow these steps:

  • Install Air by downloading the appropriate binary for your operating system from the GitHub release page or by building the tool directly from source.
  • Create a configuration file for Air in your project directory. This file can be named, for example, .air.toml or air.conf. Here's a sample configuration file that works with Fiber:
# .air.toml
root = "."
tmp_dir = "tmp"
cmd = "go build -o ./tmp/main ."
bin = "./tmp/main"
delay = 1000 # ms
exclude_dir = ["assets", "tmp", "vendor"]
include_ext = ["go", "tpl", "tmpl", "html"]
exclude_regex = ["_test\\.go"]
  • Start your Fiber application using Air by running the following command in the terminal:

As you make changes to your source code, Air will detect them and automatically restart the application.

A complete example demonstrating the use of Air with Fiber can be found in the Fiber Recipes repository. This example shows how to configure and use Air in a Fiber project to create an efficient development environment.

How do I set up an error handler?

To override the default error handler, you can override the default when providing a Config when initiating a new Fiber instance.

app := fiber.New(fiber.Config{
ErrorHandler: func(c fiber.Ctx, err error) error {
return c.Status(fiber.StatusInternalServerError).SendString(err.Error())

We have a dedicated page explaining how error handling works in Fiber, see Error Handling.

Which template engines does Fiber support?

Fiber currently supports 9 template engines in our gofiber/template middleware:

To learn more about using Templates in Fiber, see Templates.

Does Fiber have a community chat?

Yes, we have our own Discordserver, where we hang out. We have different rooms for every subject.
If you have questions or just want to have a chat, feel free to join us via this > invite link <.

Does fiber support sub domain routing ?

Yes we do, here are some examples: This example works v2

package main

import (


type Host struct {
Fiber *fiber.App

func main() {
// Hosts
hosts := map[string]*Host{}
// API
api := fiber.New()
Format: "[${ip}]:${port} ${status} - ${method} ${path}\n",
hosts["api.localhost:3000"] = &Host{api}
api.Get("/", func(c fiber.Ctx) error {
return c.SendString("API")
// Blog
blog := fiber.New()
Format: "[${ip}]:${port} ${status} - ${method} ${path}\n",
hosts["blog.localhost:3000"] = &Host{blog}
blog.Get("/", func(c fiber.Ctx) error {
return c.SendString("Blog")
// Website
site := fiber.New()
Format: "[${ip}]:${port} ${status} - ${method} ${path}\n",

hosts["localhost:3000"] = &Host{site}
site.Get("/", func(c fiber.Ctx) error {
return c.SendString("Website")
// Server
app := fiber.New()
app.Use(func(c fiber.Ctx) error {
host := hosts[c.Hostname()]
if host == nil {
return c.SendStatus(fiber.StatusNotFound)
} else {
return nil

If more information is needed, please refer to this issue #750