THE NAME ATLAS · 01
Follow the name.
Find the layers beneath it.
Rivers, towns, capes and communities carry the marks of the people who named them—and the languages that later reshaped them. Browse the stories below, with uncertainty kept in view.
State · river · baydocumented
A name that travelled
Delaware
The state and river take their name from Delaware Bay, named in 1610 by English navigator Samuel Argall in honor of Thomas West, the third Baron de la Warr. The word “Delaware” was later also applied by outsiders to Lenape people; those histories should not be collapsed into one origin story.
Read the context +
The Delaware Bay itself had earlier names, including Dutch and Indigenous forms recorded in historical sources. The name of the bay spread to the river and then the state. DNREC notes that the Delaware name is European in origin, even though Lenape people came to be known by that name as well.
DNREC · state name and historical namingOpen source note →
Riverhistorical forms
Names before the map
Delaware River
DNREC records earlier Lenape names for the river, including Wihittuck and Sipu, translated in its feature as “river of the Lenape.” These names make visible a much older relationship with the waterway than the later Delaware label.
Read the context +
Colonial records often preserve spellings through the ears and orthographies of outsiders. The University of Delaware Water Resources Center project is a useful companion for understanding variant Indigenous, European and American names for Delaware waterways.
DNREC · University of Delaware Water Resources CenterOpen source note →
Wildlife refuge · bay shoredocumented sequence
A name transformed by translation
Bombay Hook
DNREC traces the name through a Lenape form, Mettocksinowousingh, glossed as “little tree-point,” into Dutch spellings including Boomptjes Hoeck, then a form written as Bombeys before the modern name took hold.
Read the context +
This is a reminder that a place name can change as it moves between languages. The present-day refuge east of Smyrna carries the end result of that layered history.
DNREC · etymology featureOpen source note →
Point · wildlife refugedocumented historical form
A plum on the map
Prime Hook
The early form “Pruime Hoek” is traced to Dutch words meaning “Plum Point,” a reference to beach plums in the area.
Read the context +
The spelling shifted over time, as place names often do when written by speakers of different languages. Prime Hook is a useful counterpoint to more dramatic-sounding Delaware names: some are grounded in the plants and features of the landscape.
DNREC · etymology feature; Slaughter Beach Historical SocietyOpen source note →
Riverdocumented form · unknown event
A dramatic name, an uncertain story
Murderkill River
The name appears in 1654 as “Mordane Kijhlen,” translated by DNREC as Swedish for “the murderer’s creek.” The event behind the reference is unclear. “Kill” is a Dutch word for creek, so the name is not simply a reference to killing.
Read the context +
DNREC says proposed meanings such as “mother river” or “muddy river” are rejected by the historical work it cites. The exact murder reference remains unexplained; a definitive origin story would overstate the record.
DNREC · etymology featureOpen source note →
Creek · regionunresolved
The origin remains unsettled
Brandywine Creek
DNREC describes the origin as unknown. It may be connected to an early landowner named Andrew Braindwine, though the historical work it cites notes the landowner may instead have been named after the creek.
Read the context +
Popular explanations involving a brandy-carrying ship, muddy water or a nearby ale house are discussed by DNREC, which notes that the book Dutch and Swedish Place-Names in Delaware discounts these theories.
DNREC · etymology featureOpen source note →
Community · beachdisputed / unresolved
Folklore is not proof
Slaughter Beach
No single origin is established. The Slaughter name appears on early maps for local geographic features including Slaughter Creek and Slaughter Neck. The popular massacre story is not supported by the local historical society’s review of the written record.
Read the context +
The Slaughter Beach Historical Society also examines a postmaster theory and explains why the known William Slaughter reference does not neatly fit the place and timeline. DNREC separately describes the origin as unclear and mentions a possible postmaster connection. We preserve that disagreement rather than choosing a tidy answer.
Slaughter Beach Historical Society; DNRECOpen source note →
Riverunresolved
An open question
Broadkill River
DNREC describes the origin of the Broadkill name as shrouded in mystery. The word looks descriptive to modern readers, but that is not enough to establish its historical origin.
Read the context +
This entry is intentionally short: the available source does not establish a definitive etymology.
DNREC · etymology featureOpen source note →
Cape · coastal landmarklikely, not settled
A changing name on a changing coast
Cape Henlopen
DNREC records earlier European names including Cape la Warre and Cape Cornelius. The modern form is thought to derive from a place in the Netherlands or from one of two Dutch men associated with the name.
Read the context +
The place referred to by the cape name shifted over time, and spellings changed before becoming largely standardized in the 1800s. The precise source remains uncertain.
DNREC · etymology featureOpen source note →
River · hundred · school districtpossible meaning
A name with several layers
Appoquinimink
DNREC reports that Appoquinimink may mean “wounded duck” in a Native language, while also noting that the name has appeared in many spellings and that a different water-route explanation has been proposed.
Read the context +
The word should not be presented as a settled translation. It is also the name of a historic Delaware hundred; the Public Archives says Appoquinimink Hundred was established in 1682.
DNREC; Delaware Public Archives; University of Delaware Water Resources CenterOpen source note →
Bayreported meaning
A name tied to the water
Assawoman Bay
DNREC connects the name to Indigenous words translated as “midway fishing stream.” This is a reported historical interpretation, not a complete account of the communities and language traditions connected to the bay.
Read the context +
For a wider view of Indigenous waterway names and their documentation, consult the University of Delaware Water Resources Center project and the USGS gazetteer it builds on.
DNREC; University of Delaware Water Resources CenterOpen source note →
River · coastal waterwayhistorical association
A name recorded by the 1700s
Indian River
DNREC reports that the name was in use by the 1700s and refers to the Assateague. The source does not offer a full linguistic translation, so this entry records the historical association rather than assigning a meaning.
Read the context +
This is a concise historical naming note, not a complete account of the Assateague or of present-day Indigenous communities. The wider waterway research is a useful companion, with its own source limitations noted in the source register.
DNREC · etymology feature; University of Delaware Water Resources Center draft projectOpen source note →
City · countydocumented + qualified
More than one name in one place
New Castle
DNREC says the site was an Indigenous settlement called Tamakonck, which may mean “place of the beaver.” Dutch settlers founded the present city in 1651; after English control in 1664, it was named after Newcastle in northeast England.
Read the context +
The earlier Tamakonck meaning is presented as a possibility, not a definitive translation. The modern name reflects the later English colonial layer.
DNREC · etymology featureOpen source note →
City · state capitaldocumented name path
A place-name from across the Atlantic
Dover
DNREC traces Dover to the city of Dover in southeast England. That English city’s name, in turn, is derived from an old Celtic word meaning “water.”
Read the context +
A name can travel through more than one language before it reaches the place on today’s map.
DNREC · etymology featureOpen source note →
City · historic settlementdocumented sequence
New Sweden on the Delaware
Wilmington · Fort Christina
Sweden established a colony called Nya Swerige in 1638. Its principal settlement was Fort Christina, named for Queen Christina. The fort was later renamed Fort Altena under Dutch control; the site became officially known as Wilmington in 1739.
Read the context +
The earliest fort name was Fort Elbe. The sequence is a reminder that the same place can hold multiple official names as power and language change.
DNREC · etymology featureOpen source note →
Town · historic settlementdocumented histories
Swan Valley and an English town
Lewes · Zwaanendael
The Dutch settlement called Swanendael or Zwaanendael (“Swan Valley”) stood at what is now Lewes. HCA notes that William Penn later named Lewes after an English town.
Read the context +
The two names belong to different chapters of the same place’s history: an early Dutch settlement and a later English place-name inheritance.
DNREC; Delaware Division of Historical and Cultural AffairsOpen source note →
Countiesdocumented
English county names, Delaware ground
Kent & Sussex
DNREC traces Kent and Sussex to counties in southeast England. Sussex was William Penn’s home county.
Read the context +
Downstate counties had earlier names in the colonial period, including Saint Jones and Deal, before Kent and Sussex became established.
DNREC · etymology featureOpen source note →
River · regional namehistorical link
A name from Queen Christina
Christina River
The name is connected to Fort Christina, the principal settlement of New Sweden founded in 1638 and named for Sweden’s Queen Christina.
Read the context +
The river and nearby places carry traces of the Swedish colonial chapter in northern Delaware. DNREC documents the fort’s sequence of names through Swedish, Dutch and English rule.
DNREC · etymology featureOpen source note →