Choosing a version
BirdNET-Pi Enhanced vs. Nachtzuster
There are two actively maintained BirdNET-Pi forks. They share the same detection engine and identify birds equally well — the difference is what happens to your detections afterward.
The short answer
Choose the Enhanced Version if…
- You want a modern dashboard rather than tables
- You care about charts, trends, and patterns in your data
- You want weather correlated with bird activity
- You want to review and verify uncertain detections
- You're running a Pi 4B, 400, or 5
- You'll browse your station from a phone
Choose Nachtzuster's version if…
- You want the leanest possible install
- You're on a Pi 3B+ or Zero 2 W
- You mainly feed BirdWeather and rarely open the UI
- You prefer the largest, longest-established community
- You value a minimal, stable surface over new features
Neither is a wrong answer. The Enhanced Version does more, which costs some CPU and storage; Nachtzuster's does less, on purpose, and does it reliably.
What's the same
Both forks descend from Patrick McGuire's original BirdNET-Pi and both use the same BirdNET machine learning framework with the same TFLite models. That means:
- Identification accuracy is the same. Neither fork changes the model.
- Both do 24/7 recording, automatic clip extraction, and disk-space management.
- Both integrate with BirdWeather.
- Both use the same SQLite database format, so your history moves between them.
- Both support Apprise notifications and localized species names.
- Both are free, open source, and CC BY-NC-SA 4.0 licensed.
If someone tells you one fork "detects more birds" than the other, that isn't how it works — detection is the model's job, and it's the same model.
What the Enhanced Version adds
| Capability | Enhanced | Nachtzuster |
|---|---|---|
| Real-time BirdNET identification | Yes | Yes |
| Live audio stream & spectrogram | Yes | Yes |
| BirdWeather integration | Yes | Yes |
| Redesigned responsive interface | Yes | Classic UI |
| Dark mode | Yes | — |
| Interactive charts (Chart.js) | Yes | Static graphs |
| Behavioral insights suite | Yes | — |
| Weather-correlated activity analysis | Yes | — |
| Detection review queue | Yes | — |
| Timeline day replay | Yes | — |
| Per-species detail pages | Yes | Basic |
| eBird checklist export tools | Rebuilt | Basic |
| Year in Birds report | Yes | — |
| Installable as a phone app (PWA) | Yes | — |
| Runs well on Pi 3B+ / Zero 2 W | Detection yes, reports slow | Yes |
The difference in practice
Both forks will tell you that a Northern Cardinal was detected at 6:14 a.m. with 87% confidence. The Enhanced Version is built around the next question: is that normal for this time of year, has this bird been showing up daily or has it just returned after three weeks away, does it sing earlier on warm mornings, and is 87% actually good enough to trust?
Can I switch later?
Yes, in both directions, and your detection history comes with you — the database format is shared. Switching is a few commands, not a reinstall. See the migration guide, and take a backup first.
A note on the older wiki. The original mcguirepr89 installation guide is marked deprecated and points readers to Nachtzuster's fork. That notice predates this project entirely — it isn't a statement about the Enhanced Version, which is actively maintained and regularly released.