Share and embed

Put a passage on your own page.

Two things, both free, both needing no account at either end: a link that shows the verse when you paste it, and an embed that puts the passage on your site. Nothing here asks your visitors for anything.

A link that shows the verse

Paste one of these into a message, a post or a newsletter and the preview shows the verse itself and the edition it came from, rather than a generic card.

https://www.wellspringstudy.org/read/kjv/Jas/1
https://www.wellspringstudy.org/read/kjv/Jas/1?v=2
https://www.wellspringstudy.org/read/kjv/Jas/1?v=2-5

Opening the link takes the reader to that chapter in Wellspring. They do not need an account to read it.

An embed

Copy this into your page. It is a plain <iframe>; there is nothing to install and no script to add.

<iframe
  src="https://www.wellspringstudy.org/embed/kjv/Jas/1?v=2-5"
  title="James 1:2–5 (KJV) — Wellspring"
  width="100%" height="420"
  style="border:1px solid #d3cabe;border-radius:8px;display:block"
  loading="lazy"></iframe>

In Wellspring itself you do not have to write this out: select the verses you want, then Share → Copy embed code, and the markup above is on your clipboard with the right reference in the title.

Set the height yourself. The frame does not measure its own contents, so a long chapter will scroll inside whatever box you give it. Four or five verses sit comfortably in about 420 pixels; a whole chapter wants 600 or more. Pick the number that suits the passage rather than one number for every passage.

Keep the title. It is what a screen reader announces before entering the frame, and without it a listener meets an unnamed box.

Writing an address

Both shapes read the same way: the translation, the book, the chapter, and optionally the verse or the run of verses.

Books use their standard short codes — Gen, Exod, Ps, Isa, Matt, Jas, Rev. Verse runs take a hyphen: ?v=2-5. A run that reaches past the end of a chapter is trimmed to the chapter; a verse that does not exist is dropped and you get the chapter instead. Nothing is ever quietly changed into a nearby passage that does exist.

Some of the translation codes:

Code	Text
`kjv`	King James Version, with the Apocrypha
`web`	World English Bible
`bsb`	Berean Standard Bible
`ult` · `ust`	unfoldingWord Literal and Simplified Texts
`geez`	Ge’ez — the Ethiopian and Eritrean canon
`lxx` · `brenton`	Septuagint, Greek and Brenton’s English
`vul`	Clementine Vulgate
`uhb` · `ugnt`	Hebrew Bible and Greek New Testament
`hau` · `ibo` · `yor` · `swh` · `twi` · `sna` · `nde`	Hausa, Igbo, Yorùbá, Kiswahili, Twi, chiShona, isiNdebele

The library lists every text Wellspring holds, with its edition and its rights.

The licence travels with the text

This is the part worth reading before you publish. Every text on the shelf carries its own terms, and an embed shows them in the line beneath the passage — but the obligation is yours as well as ours once the passage is on your page.

Public domain — the King James Version, the Vulgate, Brenton’s Septuagint and most of the older works. Use them as you like.
CC BY-SA 4.0 — the Ge’ez text, the unfoldingWord Literal and Simplified Texts, and several of the African-language Bibles. You must keep the attribution, and share-alike means anything you build from the text carries the same licence onward. Keeping the embed intact satisfies this; retyping the text into your own page without the attribution does not.
Its own terms — a few works, such as the Sahidic New Testament, carry a specific copyright line. It is shown under the passage; reproduce it.

If you are unsure what a particular text allows, the line beneath it in the embed is the authority, and the library records the same thing for every work.

What an embed does to your visitors

Nothing. It is worth being specific, because most embeds on the web cannot say this:

No analytics, no tracking, no cookies, no local storage.
No third-party request of any kind — no fonts, scripts or images from anywhere but Wellspring.
No sign-in, no account, no link out of the frame into a workspace.
It is not indexed: the embed points search engines at the readable page instead, so it does not compete with your own page.

If your site has a privacy or cookie page, an embedded passage adds nothing to it.

What we do not offer

Said plainly so you do not go looking:

No JSON API. Reading the text from another origin is blocked on purpose; an embed needs no such permission and a data feed is a different promise from a page.
No automatic height. The frame will not resize itself yet. Set a height.
No verse images. Wellspring’s unit of sharing is a passage with its provenance attached, not a picture of a verse.

If you hold rights, or you can help

If you believe a text here is presented wrongly, or you hold rights in one, write to rights@wellspringstudy.org with the work and the basis of the claim; it will be answered and, where warranted, corrected or removed.

If your community holds a text Wellspring lacks — a Bible in a language the shelf does not carry, an oral tradition that should be recorded with its own people’s consent rather than without it — that is the more interesting letter, and the same address reaches a person.