Synopsis #
The official download.FreeBSD.org and pkg.FreeBSD.org services are normally preferable to a manually selected mirror. They use project infrastructure, GeoDNS, and content delivery to direct requests. A fixed regional host can remove automatic fallback and can become stale or unavailable.
Mirror selection also depends on the object being retrieved. Installation images, binary packages, source repositories, and archived releases use different services.
Choose the service first #
| Material | Preferred service |
|---|---|
| Installation images and release sets | https://download.FreeBSD.org/ |
| Binary packages | The configured pkg.FreeBSD.org repository through pkg |
| Source, Ports, and documentation Git repositories | https://git.FreeBSD.org/ |
| Historical, unsupported releases | http://ftp-archive.FreeBSD.org/ |
ftp.FreeBSD.org carries the same content as download.FreeBSD.org, but the official mirror appendix recommends the download name. HTTPS is preferable for ordinary image downloads.
Use automatic selection by default #
During installation, selecting the main download.FreeBSD.org GeoDNS entry routes the request automatically. For packages, retain the official repository URL and its mirror configuration unless evidence shows a persistent routing problem.
Inspect the effective package repository before changing it:
$ pkg -vv
$ pkg repositories
A package failure can instead indicate an unsupported release, an incorrect ABI, stale metadata, DNS failure, or a branch mismatch. Follow the package repository and ABI troubleshooting guide before pinning a server.
Select a fixed mirror only with evidence #
The official mirror appendix lists community-operated mirrors and their advertised protocols, but warns that the protocol list may not be current. Before using one, confirm:
- The exact release, architecture, and file exist.
- The mirror serves a current copy of the official checksum files.
- HTTPS is available when required by local policy.
- A documented fallback exists if the mirror becomes unavailable.
Use a fixed mirror as a measured exception, not as a permanent performance assumption. Record why it was selected and periodically compare it with the main service.
Verify downloaded release media #
Download the checksum file from the official release directory through a trusted connection. Calculate the digest of the image locally:
$ sha256 FreeBSD-15.1-RELEASE-amd64-memstick.img
Compare the complete digest and filename with the published value. A matching digest detects download corruption when the checksum source is trusted. For authenticity independent of the transport, verify the signed checksum file using a locally trusted FreeBSD release-engineering key and the procedure linked from the release page.
Package downloads are handled and signature-checked by pkg according to the repository configuration. Do not replace that workflow with manual package downloads to work around an unexplained repository error.