Hugo
Open-source static site generator written in Go that builds websites from Markdown and templates.
HN commenters like Hugo for fast builds and fast-loading static sites1234, cheap low-maintenance hosting5678, and as a replacement for WordPress on blogs and company sites.91011 The most common complaints are its hard-to-learn templating syntax and overall complexity12131415, plus upgrades that break older sites.161718
Why people recommend it
Speed · 3
Commenters call it the fastest mainstream SSG, and their sites score well on speed tests.
“Hugo. It's the fastest of the mainstream SSGs (single Go binary, no Node toolchain)”
“I use Hugo published to Github Pages for my blog.”
Show 1 more
“I love using hugo.”
Cheap hosting · 3
Static output makes hosting cheap or free, with little maintenance or security risk.
“Static site generators like Hugo are great.”
“My go-to is Hugo but it is somewhat complex”
Show 1 more
“It was a great move; I couldn't be happier.”
WordPress replacement · 3
Several teams and bloggers moved from WordPress and are happier with plugin-free sites.
“I wouldn’t drop WordPress for Astro - but I did for Hugo. Never been happier.”
“I moved to Hugo and encourage others to do so”
Show 1 more
“Claude made short work of porting to Hugo and Google speed rankings were excellent even without cdn etc”
Customization · 3
Custom themes, shortcodes and Pipes allow interactive posts, multiple layouts and automatic image srcsets.
“I use hugo to build my website and I wrote my own theme. It's clunky, but control over the design/build lets me:”
“My site is built with Hugo”
Show 1 more
“I use Hugo as well. If any of your pages have larger media, look into Pipes”
Ease of use · 3
Some find it simple and easy to use, with many themes, including after moving from Jekyll.
“Hugo (gohugo.io), I use it on my personal website. It has a lot of themes/plugins and very easy to use.”
“I feel Hugo is much simpler.”
Show 1 more
“I use Hugo for one blog [1] and Zola for another [2], I think they're both pretty simple to use”
Markdown files · 3
Content lives in plain Markdown files that are easy to keep and recover.
“A simple directory with markdown files and hugo blog allows me to do that.”
“I use still use hugo to generate my personal site automatically from markdown”
Show 1 more
“I just use Hugo, and I use Claude to fix the css.”
Caveats and dissent
Template syntax · 3
The templating syntax is described as annoying, verbose and hard to learn.
“I tend to use Hugo[2] the most these days, which is fast and has solid documentation”
“About a year ago I converted my 500+ post Jekyll blog to Hugo, overall it's been a net win”
Show 1 more
“Hugo. It's the fastest of the mainstream SSGs (single Go binary, no Node toolchain)”
Complexity · 3
Some found it overengineered or too complex for simple blogs and non-expert users.
“Hugo just looked like far too overengineered for what I wanted”
“My go-to is Hugo but it is somewhat complex”
Show 1 more
“Hugo that is reserved for experienced Linux devs and no one else”
Breaking upgrades · 3
New versions can break old projects, so some users pin Hugo versions.
“I moved away from Hugo because I was tired of it breaking backwards compatibility.”
“pulled in the repo + version locked Hugo + themes”
Show 1 more
“I have tried to follow Hugo's development but lost track with its constant evolution and addition of features I do not need”
Poor error feedback · 1
One user said builds could silently omit parts of the site without useful feedback.
“I moved to Hugo after years of suffering long builds.”
Often compared with
Who recommends it in their own words
Threads where it came up
- Removing Next.js Got My Blog to 100 on Every Lighthouse Category 7 mentions
- Jeffgeerling.com has been Migrated to Hugo 7 mentions
- Ask HN: Is WordPress the best way to create new websites for beginner 5 mentions
- Ask HN: Best Blogging Platform? 2 mentions
- Ask HN: What static website generator should I use in 2026? 2 mentions
- Moving from WordPress to Jekyll (and static site generators in general) 2 mentions
Data: hugo.json. Quotes are verbatim; the verdict and theme labels are written by a model from these comments, and every clause links to its sources.
All comments 43
“Hugo as the website framework”
“different SSGs (Astro, Hugo, Zola, Lume)”
“I moved away from Hugo because I was tired of it breaking backwards compatibility.”
“I use Hugo as well. If any of your pages have larger media, look into Pipes”
“Claude made short work of porting to Hugo and Google speed rankings were excellent even without cdn etc”
“I use Hugo published to Github Pages for my blog.”
“I love using hugo.”
“I use Hugo for one blog [1] and Zola for another [2], I think they're both pretty simple to use”
“Hugo that is reserved for experienced Linux devs and no one else”
“Hugo for static site generation”
“I've used Hugo and Jekyll before but everytime there is something you have to learn or get used to”
“ended up creating my own setup with Hugo”
“Static site generators like Hugo are great.”
“I would really suggest you check out Hugo.”
“I use hugo to build my website and I wrote my own theme. It's clunky, but control over the design/build lets me:”
“My go-to is Hugo but it is somewhat complex”
“I tend to use Hugo[2] the most these days, which is fast and has solid documentation”
“start with something more low-level and barebones like a static site generator (Jekyll, Hugo, Gatsby, etc.)”
“Personally, I enjoy Hugo, a Go based static site generator.”
“Jekyll would an alternative for Hugo.”
“Bearblog and Hugo are popular ones.”
“I use still use hugo to generate my personal site automatically from markdown”
“I host 10+ (Hugo) websites there”
“My site is built with Hugo”
“Hugo. It's the fastest of the mainstream SSGs (single Go binary, no Node toolchain)”
“Hugo (gohugo.io), I use it on my personal website. It has a lot of themes/plugins and very easy to use.”
“I like Hugo for my personal site”
“Someone suggested I use it to upgrade my Hugo site”
“A simple directory with markdown files and hugo blog allows me to do that.”
“I'm also hosting a Hugo blog, and using a markdown editor”
“I moved to Hugo and encourage others to do so”
“I moved to Hugo after years of suffering long builds.”
“I'm using hugo, not jekyll.”
“I wouldn’t drop WordPress for Astro - but I did for Hugo. Never been happier.”
“I feel Hugo is much simpler.”
“This has inspired me to move my personal blog to Hugo aswell.”
“Tried to migrate to Hugo from Jekyll multiple times and have bounced off every time.”
“About a year ago I converted my 500+ post Jekyll blog to Hugo, overall it's been a net win”
“It was a great move; I couldn't be happier.”
“Hugo just looked like far too overengineered for what I wanted”
“pulled in the repo + version locked Hugo + themes”
“I love static sites because they're low maintenance. Hugo and a theme would be good.”
“I have tried to follow Hugo's development but lost track with its constant evolution and addition of features I do not need”