Skip to content
FixSecurityHeadersScan a site

How to add X-Content-Type-Options on Next.js

Last updated · Reviewed by a CISSP-certified security practitioner

To add X-Content-Type-Options on Next.js, set the header in next.config.js with the value nosniff. Stops browsers from guessing (sniffing) file types. Restart dev server or redeploy. Then confirm it with curl -I or a free FixSecurityHeaders scan.

What does X-Content-Type-Options do?

Setting nosniff makes the browser trust the Content-Type you send instead of guessing, so an uploaded text file can't be executed as script.

Risk if missing: MIME sniffing can turn user uploads or JSON responses into executable scripts or styles.

What is the Next.js configuration?

Add this to next.config.js:

next.config.js
// next.config.js
module.exports = {
  poweredByHeader: false,
  async headers() {
    return [
      {
        source: "/(.*)",
        headers: [
          { key: "X-Content-Type-Options", value: "nosniff" },
        ],
      },
    ];
  },
};

How do I add it step by step?

  1. Open next.config.js.
  2. Paste the X-Content-Type-Options configuration shown below.
  3. Restart dev server or redeploy.
  4. Run curl -I https://yourdomain.com and look for the x-content-type-options line.
  5. Scan your site on FixSecurityHeaders to confirm the grade improved.

How do I verify it worked?

terminal
curl -sI https://yourdomain.com | grep -i "x-content-type-options"
# expected:
# x-content-type-options: nosniff

Check your site now

Free scan, instant grade, exact fixes for your stack.

What are the common mistakes?

  • Make sure your server sends correct Content-Type headers, or some assets will stop loading.
  • For nonce-based CSP use middleware.ts instead of static headers.
  • poweredByHeader: false removes X-Powered-By.

Quick reference

HeaderX-Content-Type-Options
Recommended valuenosniff
StackNext.js
Wherenext.config.js
ComplianceOWASP ASVS V14.4.4, SOC 2 CC6.8

FAQ

What value should I use for X-Content-Type-Options?

A safe default is nosniff. Make sure your server sends correct Content-Type headers, or some assets will stop loading.

Why isn't X-Content-Type-Options showing up on Next.js?

For nonce-based CSP use middleware.ts instead of static headers. Also clear any CDN or page cache, and check you edited the config that actually serves your domain.

Does X-Content-Type-Options affect SEO or performance?

No measurable performance cost — it's a few bytes per response. It doesn't affect rankings directly, but a misconfigured policy can break page resources, so test before enforcing.

Which compliance frameworks reference X-Content-Type-Options?

OWASP ASVS V14.4.4, SOC 2 CC6.8.

Related guides