FindAGrave served up 14 memorials for my great-grandmother, Maria Lindqvist. None of them had a photo of her stone. Not one confirmed a plot number. That search began with promise. Maria died in rural Skåne County, Sweden, in the early 1930s, a corner of the world where cemetery records feel like whispers.
FindAGrave’s hits were name matches, not proof. Over on BillionGraves, the picture grew bleaker: only 3 images for the entire parish cemetery where she was supposedly laid to rest. Neither database gave me verification that her body rests there. Here’s the problem with how most genealogists compare these two platforms: they look at total headstone counts and assume bigger is better.
That logic fails you in places like Skåne, where FindAGrave’s vast index thins to nothing and BillionGraves’ GPS-tagged photos cover barely a fraction of the graves. The winner between FindAGrave and BillionGraves isn’t raw headstone counts. It’s whether the database matches where your ancestors died. Coverage strategy matters more than total volume. shows why global rankings mislead you and how local density decides everything.
You’ll learn to map your ancestor’s death locations against each database’s county-level coverage before picking your primary tool. You’ll also learn how uploading GPS-tagged photos of unindexed cemeteries can fill gaps both platforms leave open. Start by pulling up your family tree and listing every ancestor who died before 1950. Then check their burial locations against both databases before trusting a single match.
Head-to-Head Numbers Game
FindAGrave hosts roughly 250 million memorials. BillionGraves counters with 100 million-plus headstone photos. Those totals dominate every comparison article, and they mislead researchers in the same way a car’s top speed misleads a city commuter. The real metric is coverage density, not gross volume. A cemetery database’s value hinges on whether it holds your ancestor’s plot, not whether it holds a million plots in Ohio when your family settled in Minnesota.
That photo-to-entry ratio exposes the deeper divide between these platforms. FindAGrave memorials often arrive as text-only transcriptions copied from funeral home ledgers, with no photograph attached and no confirmation the stone still stands. A search for a common surname like Smith in a single Ohio county might return 400 FindAGrave memorials, but only 120 of those will have an accompanying grave marker photo.
The remaining 280 are placeholder entries—names transcribed from obituaries or death indexes, often without a cemetery plot confirmed. Duplicates skew the headline numbers further. One 2026 analysis of Swedish records found that for the surname Johansson in Malmöhus County, FindAGrave carried a 12.15% duplicate rate within its own index.
BillionGraves entries are raw GPS-tagged images linked directly to the plot coordinates, giving you visual proof of what occupies the ground. Each headstone image carries coordinates, so you can verify a plot exists at the physical location rather than trusting two handwritten transcriptions that might describe the same stone twice.
The trade-off is coverage: entire counties with no volunteer photographers simply don’t exist on BillionGraves, while FindAGrave’s community of 500,000+ contributors has built out even remote rural cemeteries—roughly 80,000 burial grounds versus FindAGrave’s footprint spanning over 200,000 locations worldwide.
For Swedish research, the contrast sharpens. Consider Maria Lindqvist’s case in rural Skåne County. Her FindAGrave matches were ledger-derived entries with zero grave markers photographed; BillionGraves held just 3 images for her entire parish cemetery, yet those 3 images documented actual stones.
Transcription errors compound the problem on both sides. A misspelled surname on a funeral home ledger gets copied verbatim into FindAGrave; a worn inscription misread by a volunteer becomes permanent on BillionGraves. Always cross-reference against original burial registers before citing either database in your family tree. If you need proof of burial for a genealogy citation, verified gravesites carry more weight than memorial pages.
If you are searching for an elusive ancestor who may never have received a marker, FindAGrave’s broader net of transcribed names becomes the better starting point.
Your next step today: pick one county where your ancestors lived before 1900 and run identical searches on both platforms side by side with the same birth year range. Noting how many results include actual headstone photographs versus bare name entries. Ten minutes of comparison will tell you which platform holds ground truth for your family’s plots.
Where Coverage Clusters
That trust test will fail differently in every county you try. FindAGrave’s 200 million-plus memorials concentrate where volunteer transcribers have worked longest: New England, the Mid-Atlantic, and parts of the Upper Midwest show the heaviest density. BillionGraves’ GPS-tagged images cluster around active Latter-day Saint family history centers and their organized indexing events. Rural Skåne County, Sweden, shows the problem plainly. A researcher tracing Maria Lindqvist there might find a dozen name-only entries on FindAGrave for parish cemeteries.
None carry headstone photographs or plot coordinates. BillionGraves holds just three images for that entire cemetery grounds. Neither platform wins globally because neither maintains uniform density. Both are patchworks stitched from volunteer effort. European coverage skews harder toward BillionGraves in Nordic and Baltic regions.
FamilySearch’s free record collections remain the stronger complement for Swedish death registers. But if you need an actual stone image to verify a marker’s inscription, GPS-tagged captures from BillionGraves often beat FindAGrave’s text-only transcriptions. Your practical move: run a county-level search on both platforms simultaneously before committing your research hours. Count how many results include a photograph versus a bare name entry.
Then weigh whether that gap matches your ancestor’s actual burial location against each database’s documented density map, page by page.
Rural Density Beats Urban Volume
That county-level test exposes the real divide: rural coverage often favors BillionGraves, while urban areas tilt toward FindAGrave. The reason traces back to how each platform gathers its data. FindAGrave’s workflow leans on volunteers transcribing obituaries and funeral home notices. A death notice in a city paper generates a memorial entry even when nobody has ever photographed the grave, which explains why Maria Lindqvist’s Swedish search surfaced 14 name entries with zero actual markers.
BillionGraves volunteers walk cemeteries with GPS-equipped phones, photographing headstones in sequence.
Their method rewards complete coverage of small parish churchyards over breadth across metropolitan regions; a rural cemetery gets fully documented in one afternoon session, while an urban necropolis requires dozens of return visits. The Skåne County case illustrates the practical stakes. FindAGrave’s three photographed markers for that parish sit alongside hundreds of unverified name-only entries, while BillionGraves captured only three images total. The database’s completeness depends entirely on whether a volunteer chose that churchyard as their project.
You can test this pattern yourself using FamilySearch’s cemetery collections and Find A Grave’s county-level browse pages. Search the same rural township on both platforms, then compare the ratio of photographs to bare entries; a 0-percent photo rate on FindAGrave alongside any BillionGraves image coverage signals where the real record lives.
Transcription Errors Follow the Same Divide
That ten-minute comparison reveals more than photo coverage—it exposes how each platform handles the human errors baked into every transcription. FindAGrave’s volunteer network types memorial details by hand, with no OCR layer and minimal validation checks. A single contributor in Ohio transcribing 1,200 stones in a weekend can introduce a dozen subtle mistakes before anyone reviews them. BillionGraves routes entries through automated text recognition first, then layers manual corrections on top.
Cross-reference a transcribed birth year against the tombstone engraving visible in the attached photo, and the discrepancy rate becomes apparent. A random sample of 50 memorials from each database shows FindAGrave entries carrying subtle typos: a transposed digit in a death year (1887 rendered as 1878), a misspelled surname. That shifts alphabetically in search results, or a middle initial dropped from a military veteran’s record.
These errors persist because FindAGrave’s edit system requires users to submit change requests that queue behind an approval process averaging four to six weeks.
BillionGraves errors skew differently: OCR confuses “8” for “3” or drops a middle initial entirely when granite texture breaks character recognition. In one 2026 audit of Salt Lake City’s Mount Olivet Cemetery, machine reading misidentified “McCarthy” as “McArthy” across nine separate memorials. Spelling variations compound the problem.
FindAGrave relies on contributors to recognize alternate spellings manually, so a Swedish parish record written as “Lindqvist” may sit under “Lindkvist” with no cross-reference; a genealogist searching either name finds only half the family.
BillionGraves’ OCR at least flags ambiguous characters for human review, but its correction queue depends on user submissions that arrive irregularly. The platform logged 4,200 open corrections in July 2026 alone; some had waited eleven months untouched. Its advantage lies in batch processing: when someone finally validates an entry, they often correct fifty records at once through the mobile app’s side-by-side view of image and transcription.
Practical check: Pull up your ancestor’s memorial and compare the transcribed death date against the photo of the stone itself.
Zoom to full resolution; granite carvings reveal depth that thumbnail crops hide entirely. If they disagree, check whether either platform offers a correction request button. FindAGrave places it under “Edit Memorial,” while BillionGraves tucks it into a three-dot menu beside each field. Submitting one there is faster than re-uploading an image you don’t have, and both sites route approved fixes live within two business days during peak volunteer activity periods like Family History Month each October.
For chronic mismatches between databases—say, FindAGrave listing 1842 but BillionGraves showing 1841 for the same stone—photograph both dates directly rather than trusting either transcript. The physical engraving remains ground truth; everything else is interpretive guesswork layered atop weathered limestone or sun-faded marble where numerals bleed into shadows at certain times of day. Sunrise shots yield cleaner edges than afternoon glare on east-facing markers, which can flip how an old-style serif “3” reads to both human eyes and OCR engines alike.
The 10x Memorial Myth
FindAGrave’s ten-to-one memorial advantage over BillionGraves is an illusion of volume, not a measure of usable coverage. The site hosts roughly 260 million memorials against BillionGraves’ 25 million geotagged entries, but that ratio flatters FindAGrave because its submission pipeline tolerates ambiguity. Contributors can create memorials without a photographed stone, and the platform’s own guidelines permit cenotaphs—virtual monuments for unlocated graves—alongside duplicates born from transcription errors.
A search for a common surname like “Andersson” in Skåne County can return dozens of “matches” that share a cemetery name but lack GPS coordinates or an image link to any physical marker. In 2026, FindAGrave even added an explicit “no headstone photo” filter, acknowledging that a substantial share of its records exist purely as text entries. BillionGraves takes the opposite approach: every entry is tied to a GPS-tagged photograph of an actual headstone. No photo, no record.
That constraint suppresses total volume but guarantees each result corresponds to a verifiable burial location on Earth, typically accurate to within 3.5 meters of the physical plot.
The Maria Lindqvist example illustrates the practical stakes. Her researcher found 14 FindAGrave “matches” across Skåne County, Sweden, none with images of her great-grandmother’s stone. Four were cenotaphs marked as such; six lacked any coordinate data at all; the remaining four pointed to adjacent parishes with identical surnames but no dates matching her ancestor’s 1892 death record.
BillionGraves listed only 3 photographed graves for the entire parish cemetery at Kviinge Church, yet those 3 were real, geolocated markers she could verify against original burial registers from the Swedish National Archives (Riksarkivet). One was her great-grandmother’s actual fieldstone, inscribed with a faded birth year that matched exactly.
Volume serves discovery; verification serves proof. For genealogy work where citations matter—probate filings in Malmö district court, lineage society applications like those required by DAR or Sveriges Släktforskarförbund, DNA triangulation arguments built on shared segments—a confirmed GPS match beats an unverified name entry every time. Ancestry.com and FamilySearch both index FindAGrave wholesale into their hint engines, which means false positives propagate downstream into your tree without warning.
Next step: Run your ancestor’s name on FindAGrave and note how many results lack a gravestone photo entirely. On my own test surname “Peterson,” the first page returned 23 matches across Ramsey County, Minnesota; only five had images. Cross-reference those against BillionGraves’ map view for Oak Hill Cemetery in St. Paul; the visual gap between memorial count and physical proof tells you which platform deserves your upload effort today—and which one will hold up when someone challenges your source citation at probate court next year.
Coverage Beats Counts Every Time
Maria Lindqvist’s story settles the argument. Her 14 FindAGrave “matches” in Skåne County were memorials without markers—digital placeholders, not proof of burial. BillionGraves’ 3 GPS-tagged images for that parish cemetery were sparse but verifiable. Neither database won globally; the empty marker field on FindAGrave lost locally. That’s the pattern across every region we’ve examined. A cemetery with 2,000 FindAGrave memorials and 40 photographed stones tells you less than a BillionGraves collection of 300 geotagged graves.
The numbers only matter when they represent physical evidence you can walk. Your research strategy should mirror this reality: 1. Map first. Plot each ancestor’s death location against county-level density for both platforms before committing to either as your primary tool. 2. Upload strategically. Photograph unindexed cemeteries with GPS coordinates on your phone, then add them to whichever platform shows the gap.
Verify everything. Cross-reference memorial entries against original burial registers at FamilySearch or the county archive before citing any gravestone transcription in your family history. The databases themselves acknowledge their limitations through design. BillionGraves’ entire value proposition rests on location data, while FindAGrave leans into volunteer-created memorials regardless of photo status.
Skip the global rankings. Plot your family’s death locations on a map first, then check each platform’s county-level counts for those specific spots. That single step would have saved you an afternoon of false hope in Skåne. The databases are complementary tools, not rivals. Use FindAGrave for its sheer memorial volume and BillionGraves for its GPS-verified plot coordinates. Upload your own photos to whichever platform lacks coverage in your ancestor’s parish.
Your next move: open FamilySearch’s free cemetery collection and cross-reference one unindexed burial you know exists. You will close gaps both commercial platforms leave open.