Map Link Generator

Build portable map and directions links from coordinates, an address, or place text for Google Maps, Apple Maps, Waze, Bing Maps, OpenStreetMap and geo URIs—without a WebToolArc geocoding API call.

Coordinates · address text · directions · provider audit · batch export

Map Link & Directions Studio

Generate provider-specific URLs locally, inspect what each provider can encode, and hand off single locations or route destinations without sending your input to a WebToolArc geocoder.

Portable map-link studio

Google Maps URLs v1Apple · Waze · Bing · OSMLocation + directionsBatch CSV / JSONExplicit save + reproducible link

ActionDestination inputCoordinate precisionMap zoom

LatitudeLongitude

Optional labelOptional Google Place ID

Ready.

Provider link audit

—generated links

—action

—input semantics

—longest URL chars

Provider / support	Generated URL	Action

Portable project handoff

Project JSON contains the current inputs and generated URLs. “Save locally” is explicit-only and keeps at most 12 projects in this browser. A reproducible link places the entered location and route settings in its query string.

#	Destination	Saved
No explicitly saved projects.

Calculation / URL audit

Batch location links

One row per line. Use Label|latitude|longitude for deterministic coordinate links or Label|address/place text for provider-side search/geocoding. Blank rows are ignored.

Batch not run yet.

Line	Label	Google	Apple

Truth boundaries

WebToolArc constructs URLs locally. It does not geocode free-text addresses, verify that a business exists, fetch route distance/time, or confirm that a third-party provider resolves a query to the intended place.
Coordinates are range-validated here. Free-text address/place inputs are passed to the chosen provider, which performs its own search or geocoding after you open the link.
Google links follow the documented Maps URLs api=1 scheme. A supplied Google Place ID is user-provided; this page does not look one up.
Apple’s published Map Links reference supports driving, walking and transit flags. When bicycling is selected, the Apple URL intentionally omits a transport flag rather than inventing an unsupported value.
Waze destination deep links do not encode a custom origin in this studio. OpenStreetMap output is a destination map/search link, not a route claim. Geo URI handling depends on the receiving device/app.
Bing’s documented custom URL parameters are used, but Microsoft notes those parameters can change. Always test links in the target environment before publishing them at scale.

One location, different provider URL contracts

A map link is not a universal binary format. Google Maps, Apple Maps, Waze, Bing Maps and OpenStreetMap accept different parameters and do not promise identical search, routing or app-opening behavior. This studio exposes those differences instead of pretending every generated URL is equivalent.

Worked coordinate check

For 33.800671,-117.920873, the coordinate itself is deterministic: WebToolArc can validate the latitude/longitude range and encode the same point into provider-specific URL syntax. The final map tiles, place label, route choice, traffic and travel time remain third-party results.

Verification: inspect the generated URL before opening it. For Google, confirm api=1 and the encoded query/destination. For coordinate links, confirm the numeric latitude and longitude survive the handoff.

Address text is intentionally different from coordinates

When you enter an address or place name, this page does not call a geocoding service. It URL-encodes the text and hands it to the provider. That keeps the generator local and API-key-free, but it also means the provider decides which real-world result matches the text.

Directions need provider-specific truth boundaries

Google, Apple and Bing expose documented direction parameters, while Waze focuses on destination navigation. OpenStreetMap output here remains a map/search handoff rather than silently inventing a routing contract.