If you are not sure if the website you would like to visit is secure, you can verify it here. Enter the website address of the page and see parts of its content and the thumbnail images on this site. None (if any) dangerous scripts on the referenced page will be executed. Additionally, if the selected site contains subpages, you can verify it (review) in batches containing 5 pages.
favicon.ico: docs.syncthing.net/dev/building.html - Building Syncthing  Syncthing .

site address: docs.syncthing.net/dev/building.html redirected to: docs.syncthing.net/dev/building.html

site title: Building Syncthing Syncthing documentation

Our opinion (on Tuesday 17 November 2026 6:41:04 UTC):

GREEN status (no comments) - no comments
After content analysis of this website we propose the following hashtags:



Meta tags:

Headings (most frequently used words):

building, and, syncthing, branches, tags, prerequisites, unix, windows, subcommands, options, version, tagging, without, git, navigation, related, topics, quick, search, donate, support,

Text of the page (most frequently used words):
the (67), build (42), #syncthing (36), you (27), and (24), for (20), run (20), git (14), version (13), with (13), will (11), building (10), from (10), current (9), can (9), your (9), release (8), this (8), built (8), source (8), windows (8), dev (8), tar (7), upgrade (7), when (7), github (6), use (6), binary (6), cross (6), should (6), that (5), file (5), tags (5), zip (5), goos (5), have (5), development (4), builds (4), are (4), package (4), upstream (4), https (4), fetch (4), not (4), commands (4), note (4), bin (4), binaries (4), below (4), compiling (4), cgo_enabled (4), linux (4), goarch (4), directory (4), parameters (4), what (4), need (4), compiler (4), install (4), work (4), api (3), distribution (3), something (3), debian (3), tarball (3), example (3), instead (3), flag (3), remote (3), add (3), com (3), all (3), code (3), branch (3), main (3), default (3), commit (3), tag (3), see (3), zig (3), 386 (3), options (3), creates (3), fpm (3), target (3), unless (3), userprofile (3), now (3), prerequisites (3), going (3), latest (3), next (2), debugging (2), previous (2), working (2), web (2), gui (2), documentation (2), automatic (2), introduction (2), usage (2), written (2), tagged (2), upgrades (2), disabled (2), want (2), system (2), being (2), our (2), without (2), repository (2), probably (2), only (2), overridden (2), variable (2), unix (2), build_user (2), builder (2), build_host (2), buildhost (2), local (2), most (2), username (2), hostname (2), environment (2), dist (2), assumes (2), otherwise (2), same (2), considerations (2), subcommand (2), unixy (2), requires (2), using (2), subcommands (2), goes (2), wrong (2), ready (2), pick (2), place (2), grab (2), clone (2), time (2), open (2), android (2), information (2), downloaded (2), implementation (2), sqlite (2), usually (2), stable (2), own (2), donate, support, quick, search, overview, related, topics, specifications, http, utility, services, event, rest, signing, creating, issue, management, infrastructure, understanding, device, ids, crash, reporting, developers, navigation, gf020590, edit, page, arch, installed, rpm, almost, certainly, well, prevent, activated, perfectly, fine, course, server, contains, called, informs, different, one, automatically, generated, must, pass, rebuild, fails, error, did, happen, forking, select, option, copy, fork, these, string, invalid, addition, timestamp, taken, epoch, seconds, source_date_epoch, 2020, utc, derived, recent, replaced, variables, tagging, non, trivial, nonetheless, try, possible, ease, pain, check, inspiration, workflows, architecture, upgrading, given, influence, examples, deb, runs, tests, test, just, named, compile, platform, let, know, how, invoke, controls, together, x86_64, amd64, installs, command, happens, any, following, exist, exe, window, cmd, mkdir, inside, right, terminal, already, developer, easiest, way, get, download, instructed, doc, ndk, executables, installing, recommended, order, properties, icon, compiled, goversioninfo, packages, required, installation, includes, marker, don, skip, make, sure, while, succeed, resulting, significantly, lower, performance, higher, memory, couldn, used, users, thank, uses, storing, data, common, also, older, versions, likely, largely, follows, policy, looking, contents, may, unstable, unsuitable, general, consumption, base, doing, into, always, pull, requests, based, branches, still, prefer, aware, there, mechanism, overwrite, avoid, but, responsible, through, process, special, packaging, other, purposes, recommend, official, releases,


Text of the page (random words):
building syncthing syncthing documentation building syncthing note you probably only need to go through the build process if you are going to do development on syncthing or if you need to do a special packaging of it for all other purposes we recommend using the official binary releases instead if you still prefer to build syncthing from source for your own use be aware that there is a built in automatic upgrade mechanism that will overwrite your built binary with a downloaded version to avoid this you can use the no upgrade build flag see below but you will be responsible for your own upgrades branches and tags you should base your work on the main branch when doing your development this branch is usually what will be going into the next release and always what pull requests should be based on if you re looking to build and package a release of syncthing you should instead use the latest tag vx y z as the contents of main may be unstable and unsuitable for general consumption prerequisites the latest stable version of go the previous stable version should also work older versions will likely not work this largely follows go s release policy usually a c compiler syncthing uses sqlite for storing data and the most common implementation is written in c note don t skip the c compiler and make sure to build syncthing with cgo_enabled 1 if you are cross compiling while the build will succeed with cgo_enabled 0 and the resulting binary will work it will run with significantly lower performance and higher memory usage when the c implementation of sqlite couldn t be used your users will not thank you git unless you re building from a downloaded source tarball that includes a release marker with the version information if you want to build debian packages fpm is required see fpm s installation information to build windows executables installing goversioninfo is recommended in order to add file properties and icon to the compiled binaries building android binaries requires android ndk if you re not already a go developer the easiest way to get going is to download the latest version of go as instructed in https go dev doc install building unix install the prerequisites open a terminal run the commands below pick a place for your syncthing source mkdir p dev cd dev grab the code git clone https github com syncthing syncthing git now we have the source time to build cd syncthing you should be inside dev syncthing right now go run build go unless something goes wrong you will have a syncthing binary built and ready in dev syncthing bin building windows install the prerequisites open a cmd window run the commands below pick a place for your syncthing source md userprofile dev cd d userprofile dev grab the code git clone https github com syncthing syncthing git now we have the source time to build cd syncthing go run build go unless something goes wrong you will have a syncthing exe binary built and ready in userprofile dev syncthing bin subcommands and options the following build go subcommands and options exist go run build go install installs binaries in bin default command this is what happens when build go is run without any commands or parameters go run build go build builds just the named target or syncthing by default to the current directory use this when cross compiling with parameters for what to cross compile to go run build go goos linux goarch 386 build when cross compiling you need to have a c compiler for the target platform and you need to let go know how to invoke it the cc flag to build go controls this together with the environment variable cgo_enabled 1 for example to cross build from linux to windows using zig as the c compiler go run build go goos windows goarch amd64 cc zig cc target x86_64 windows build go run build go test runs the tests go run build go deb creates a debian package in the current directory requires fpm and a unixy build go run build go tar creates a syncthing tar gz dist file in the current directory assumes a unixy build otherwise same considerations and parameters as for the build subcommand go run build go zip creates a syncthing zip dist file in the current directory assumes a windows build otherwise same considerations and parameters as for the build subcommand the options no upgrade goos and goarch can be given to influence build tar and zip examples go run build go goos linux goarch 386 tar builds a tar gz distribution of syncthing for linux 386 go run build go goos windows no upgrade zip builds a zip distribution of syncthing for windows current architecture with upgrading disabled note cross compiling with c cgo_enabled 1 can be non trivial nonetheless you should try to do so when at all possible we use zig to ease the pain you can check our build workflows for inspiration version tagging the binaries are tagged with a version derived from the current git commit the most recent git tag and the current username and hostname the git commit and tag can be replaced by a release file see below the username and hostname can be overridden by the build_user and build_host environment variables for example build_user builder build_host buildhost local go run build go bin syncthing version syncthing v1 8 0 builder buildhost local 2020 07 30 11 49 14 utc in addition the timestamp by default taken from the current git commit can be overridden by the source_date_epoch variable in unix epoch seconds note if your built binary fails with an invalid version string error you probably did not fetch the git tags with the code this can happen when forking the repository on github if you select the option to copy the main branch only to fetch the tags on a fork run these commands add the upstream repository as a remote git remote add upstream https github com syncthing syncthing git fetch all tags from the upstream remote git fetch tags upstream rebuild go run build go building without git syncthing can be built perfectly fine from a source tarball of course if the tarball is from our build server it contains a file called release that informs the build system of the version being built if you re building from a different source package for example one automatically generated by github you must instead pass the version flag to build go if you are building something that will be installed as a package debian rpm you almost certainly want to use no upgrade as well to prevent the built in upgrade system from being activated go run build go version v0 10 26 no upgrade tar builds a tar gz distribution of syncthing for the current os arch tagged as v0 10 26 with upgrades disabled edit this page on github version v2 1 0 26 gf020590 written for v2 1 0 navigation introduction usage development introduction working on the web gui building syncthing debugging syncthing automatic crash reporting for developers understanding device ids syncthing infrastructure issue management creating a release release signing rest api event api http utility services api specifications related topics documentation overview development previous working on the web gui next debugging syncthing quick search donate support
Thumbnail images (randomly selected): * Images may be subject to copyright.GREEN status (no comments)
  • Logo
  • Donate

Verified site has: 16 subpage(s). Do you want to verify them? Verify pages:

1-5 6-10 11-15 16-16


The site also has references to the 1 subdomain(s)

  syncthing.net  Verify


The site also has 1 references to other resources (not html/xhtml )

 github.com/syncthing/syncthing/blob/m___.yaml  Verify


Top 50 hastags from of all verified websites.

Supplementary Information (add-on for SEO geeks)*- See more on header.verify-www.com

Header

HTTP/1.1 301 Moved Permanently
Connection close
Content-Length 162
Server GitHub.com
Content-Type text/html
Location htt????/docs.syncthing.net/dev/building.html
X-GitHub-Request-Id C608:2173AB:1F3F400:1F73085:6AFBF700
x-github-edge-region fra
Accept-Ranges bytes
Age 0
Date Tue, 17 Nov 2026 06:41:04 GMT
Via 1.1 varnish
X-Served-By cache-rtm-ehrd2290058-RTM
X-Cache MISS
X-Cache-Hits 0
X-Timer S1794897664.446468,VS0,VE118
Vary Accept-Encoding
X-Fastly-Request-ID f6ea7c13ef8a8a4c4c7a301fcd98fabe76b98c94
HTTP/2 200
server GitHub.com
content-type text/html; charset=utf-8
last-modified Wed, 21 Oct 2026 07:53:48 GMT
access-control-allow-origin *
etag W/ 6ad86f8c-546b
expires Tue, 17 Nov 2026 06:51:04 GMT
cache-control max-age=600
content-encoding gzip
x-proxy-cache MISS
x-github-request-id 7D3C:349C84:2CA64F:2ED876:6AFBF700
x-github-edge-region uksouth
accept-ranges bytes
age 0
date Tue, 17 Nov 2026 06:41:04 GMT
via 1.1 varnish
x-served-by cache-lcy-egml8630075-LCY
x-cache MISS
x-cache-hits 0
x-timer S1794897665.592215,VS0,VE100
vary Accept-Encoding
x-fastly-request-id 8c330221f1c1dc9c1fbb156e9150b90a35ae1109
content-length 5410

Meta Tags

title="Building Syncthing Syncthing documentation"
charset="utf-8"
name="viewport" content="width=device-width, initial-scale=1.0"
name="viewport" content="width=device-width, initial-scale=1"

Load Info

page size5410
load time (s)0.262125
redirect count1
speed download20648
server IP 185.199.108.153
* all occurrences of the string "http://" have been changed to "htt???/"