Text Run
A contiguous run of text. Strings cover unformatted spans; object form adds character formatting.
Metadata
Field index
This definition uses the forms or value constraints below.
oneOf 1 · string
Exact constraints for oneOf 1
{
"type": "string"
}oneOf 2 · object
| Field | Type | Req. | Default | Description |
|---|---|---|---|---|
| text | string | yes | — | Text for this run. |
| bold | boolean | — | — | Whether the run is rendered in bold. |
| italic | boolean | — | — | Whether the run is rendered in italic. |
| underline | boolean | — | — | Whether the run is underlined. |
| strikethrough | boolean | — | — | Whether the run is rendered with a strikethrough line. |
| color | string | — | — | Run text color. Documented forms: a hex string ('#RGB', '#RRGGBB', '#RRGGBBAA'), a color-scheme slot or role name resolved through the effective color scheme ('accent2', 'text'), or a 'var:<id>' reference into the top-level variables map. Prefer names over hex so runs survive re-theming. Any other string stays schema-valid so imported decks keep validating: validators warn and renderers fall back to the theme text color. |
| fontSize | number | — | — | Requested run font size in points. |
| fontFamily | string | — | — | Run font family override. It wins over the code font a run with 'code' takes. |
| code | boolean | — | — | Whether the run is an inline code span: it is drawn in the design's code font (design.fontScheme.code, else the resolved font scheme's code family, else Roboto Mono), unless the run names its own fontFamily. Only the font changes; there is no background, because a PPTX run cannot have one. Markdown backticks read and write code runs. |
| lang | string | — | — | BCP-47 language tag of the run, such as 'fr-FR' or 'ja-JP', when it differs from the deck language. It sets the proofing language (PPTX a:rPr lang) and the language the run's script fonts and glyph variants follow (for example the Japanese or the Simplified Chinese face for Han characters); without it the run follows the deck language. |
| link | string | — | — | URL to link the run text to: an http(s) URL, a 'mailto:' address or a 'tel:' number, without whitespace. The preview draws it as a link and PPTX export writes a native hyperlink for all three; any other scheme is not valid. |
| superscript | boolean | — | — | Whether the run is rendered as superscript. |
| subscript | boolean | — | — | Whether the run is rendered as subscript. |
| cite | string | array<string> | — | — | One or more ids from the top-level references list that this run cites. Engines draw a superscript marker ('1', or '1,2' for several ids) directly after the run and list '<n> <reference text>' in the slide's footnote area; markers are numbered per deck in order of first use, and the same id keeps its number. An id missing from references is a validation error (cite-unknown-reference). Supported in text, bullets and list item runs, in the slide title, subtitle and tag, and in the quote text. |
| footnote | string | array<ref:TextRun> | — | — | An inline note for this run, without a references entry. Engines draw a superscript marker after the run and list the note in the slide's footnote area; every footnote takes a new number in the deck's marker sequence. Supported in text, bullets and list item runs, in the slide title, subtitle and tag, and in the quote text. |
text
typestringrequiredyesdefault—
Text for this run.
{
"text": "Hello, "
}bold
typebooleanrequirednodefault—
Whether the run is rendered in bold.
italic
typebooleanrequirednodefault—
Whether the run is rendered in italic.
underline
typebooleanrequirednodefault—
Whether the run is underlined.
strikethrough
typebooleanrequirednodefault—
Whether the run is rendered with a strikethrough line.
color
typestringrequirednodefault—
Run text color. Documented forms: a hex string ('#RGB', '#RRGGBB', '#RRGGBBAA'), a color-scheme slot or role name resolved through the effective color scheme ('accent2', 'text'), or a 'var:<id>' reference into the top-level variables map. Prefer names over hex so runs survive re-theming. Any other string stays schema-valid so imported decks keep validating: validators warn and renderers fall back to the theme text color.
{
"color": "#0F172A"
}fontSize
typenumberrequirednodefault—
Requested run font size in points.
fontFamily
typestringrequirednodefault—
Run font family override. It wins over the code font a run with 'code' takes.
{
"fontFamily": "Inter"
}code
typebooleanrequirednodefault—
Whether the run is an inline code span: it is drawn in the design's code font (design.fontScheme.code, else the resolved font scheme's code family, else Roboto Mono), unless the run names its own fontFamily. Only the font changes; there is no background, because a PPTX run cannot have one. Markdown backticks read and write code runs.
lang
typestringrequirednodefault—pattern^[A-Za-z]{2,8}(-[A-Za-z0-9]{1,8})*$
BCP-47 language tag of the run, such as 'fr-FR' or 'ja-JP', when it differs from the deck language. It sets the proofing language (PPTX a:rPr lang) and the language the run's script fonts and glyph variants follow (for example the Japanese or the Simplified Chinese face for Han characters); without it the run follows the deck language.
{
"lang": "fr-FR"
}link
typestringrequirednodefault—pattern^(https?://|mailto:|tel:)\S+$
URL to link the run text to: an http(s) URL, a 'mailto:' address or a 'tel:' number, without whitespace. The preview draws it as a link and PPTX export writes a native hyperlink for all three; any other scheme is not valid.
{
"link": "https://acme.com"
}superscript
typebooleanrequirednodefault—
Whether the run is rendered as superscript.
subscript
typebooleanrequirednodefault—
Whether the run is rendered as subscript.
cite
typestring | array<string>requirednodefault—
One or more ids from the top-level references list that this run cites. Engines draw a superscript marker ('1', or '1,2' for several ids) directly after the run and list '<n> <reference text>' in the slide's footnote area; markers are numbered per deck in order of first use, and the same id keeps its number. An id missing from references is a validation error (cite-unknown-reference). Supported in text, bullets and list item runs, in the slide title, subtitle and tag, and in the quote text.
{
"cite": "gartner-2026"
}footnote
typestring | array<ref:TextRun>requirednodefault—
An inline note for this run, without a references entry. Engines draw a superscript marker after the run and list the note in the slide's footnote area; every footnote takes a new number in the deck's marker sequence. Supported in text, bullets and list item runs, in the slide title, subtitle and tag, and in the quote text.
{
"footnote": "Excludes the discontinued hardware line."
}Exact constraints for oneOf 2
{
"type": "object",
"required": [
"text"
],
"properties": {
"text": {
"type": "string",
"description": "Text for this run.",
"examples": [
"Hello, ",
"world"
]
},
"bold": {
"type": "boolean",
"description": "Whether the run is rendered in bold."
},
"italic": {
"type": "boolean",
"description": "Whether the run is rendered in italic."
},
"underline": {
"type": "boolean",
"description": "Whether the run is underlined."
},
"strikethrough": {
"type": "boolean",
"description": "Whether the run is rendered with a strikethrough line."
},
"color": {
"type": "string",
"description": "Run text color. Documented forms: a hex string ('#RGB', '#RRGGBB', '#RRGGBBAA'), a color-scheme slot or role name resolved through the effective color scheme ('accent2', 'text'), or a 'var:<id>' reference into the top-level variables map. Prefer names over hex so runs survive re-theming. Any other string stays schema-valid so imported decks keep validating: validators warn and renderers fall back to the theme text color.",
"examples": [
"#0F172A",
"accent2",
"var:risk"
]
},
"fontSize": {
"type": "number",
"exclusiveMinimum": 0,
"description": "Requested run font size in points."
},
"fontFamily": {
"type": "string",
"description": "Run font family override. It wins over the code font a run with 'code' takes.",
"examples": [
"Inter",
"Source Serif Pro",
"JetBrains Mono"
]
},
"code": {
"type": "boolean",
"description": "Whether the run is an inline code span: it is drawn in the design's code font (design.fontScheme.code, else the resolved font scheme's code family, else Roboto Mono), unless the run names its own fontFamily. Only the font changes; there is no background, because a PPTX run cannot have one. Markdown backticks read and write code runs."
},
"lang": {
"type": "string",
"pattern": "^[A-Za-z]{2,8}(-[A-Za-z0-9]{1,8})*$",
"description": "BCP-47 language tag of the run, such as 'fr-FR' or 'ja-JP', when it differs from the deck language. It sets the proofing language (PPTX a:rPr lang) and the language the run's script fonts and glyph variants follow (for example the Japanese or the Simplified Chinese face for Han characters); without it the run follows the deck language.",
"examples": [
"fr-FR",
"ja-JP",
"de"
]
},
"link": {
"type": "string",
"pattern": "^(https?://|mailto:|tel:)\\S+$",
"description": "URL to link the run text to: an http(s) URL, a 'mailto:' address or a 'tel:' number, without whitespace. The preview draws it as a link and PPTX export writes a native hyperlink for all three; any other scheme is not valid.",
"examples": [
"https://acme.com",
"https://acme.com/case-studies/beta",
"mailto:hello@acme.com",
"tel:+15551234567"
]
},
"superscript": {
"type": "boolean",
"description": "Whether the run is rendered as superscript."
},
"subscript": {
"type": "boolean",
"description": "Whether the run is rendered as subscript."
},
"cite": {
"oneOf": [
{
"type": "string",
"minLength": 1
},
{
"type": "array",
"minItems": 1,
"items": {
"type": "string",
"minLength": 1
}
}
],
"description": "One or more ids from the top-level references list that this run cites. Engines draw a superscript marker ('1', or '1,2' for several ids) directly after the run and list '<n> <reference text>' in the slide's footnote area; markers are numbered per deck in order of first use, and the same id keeps its number. An id missing from references is a validation error (cite-unknown-reference). Supported in text, bullets and list item runs, in the slide title, subtitle and tag, and in the quote text.",
"examples": [
"gartner-2026",
[
"gartner-2026",
"annual-report"
]
]
},
"footnote": {
"oneOf": [
{
"type": "string",
"minLength": 1
},
{
"type": "array",
"minItems": 1,
"items": {
"$ref": "#/$defs/TextRun"
}
}
],
"description": "An inline note for this run, without a references entry. Engines draw a superscript marker after the run and list the note in the slide's footnote area; every footnote takes a new number in the deck's marker sequence. Supported in text, bullets and list item runs, in the slide title, subtitle and tag, and in the quote text.",
"examples": [
"Excludes the discontinued hardware line."
]
}
}
}Complete definition constraints
{
"description": "A contiguous run of text. Strings cover unformatted spans; object form adds character formatting.",
"oneOf": [
{
"type": "string"
},
{
"type": "object",
"required": [
"text"
],
"properties": {
"text": {
"type": "string",
"description": "Text for this run.",
"examples": [
"Hello, ",
"world"
]
},
"bold": {
"type": "boolean",
"description": "Whether the run is rendered in bold."
},
"italic": {
"type": "boolean",
"description": "Whether the run is rendered in italic."
},
"underline": {
"type": "boolean",
"description": "Whether the run is underlined."
},
"strikethrough": {
"type": "boolean",
"description": "Whether the run is rendered with a strikethrough line."
},
"color": {
"type": "string",
"description": "Run text color. Documented forms: a hex string ('#RGB', '#RRGGBB', '#RRGGBBAA'), a color-scheme slot or role name resolved through the effective color scheme ('accent2', 'text'), or a 'var:<id>' reference into the top-level variables map. Prefer names over hex so runs survive re-theming. Any other string stays schema-valid so imported decks keep validating: validators warn and renderers fall back to the theme text color.",
"examples": [
"#0F172A",
"accent2",
"var:risk"
]
},
"fontSize": {
"type": "number",
"exclusiveMinimum": 0,
"description": "Requested run font size in points."
},
"fontFamily": {
"type": "string",
"description": "Run font family override. It wins over the code font a run with 'code' takes.",
"examples": [
"Inter",
"Source Serif Pro",
"JetBrains Mono"
]
},
"code": {
"type": "boolean",
"description": "Whether the run is an inline code span: it is drawn in the design's code font (design.fontScheme.code, else the resolved font scheme's code family, else Roboto Mono), unless the run names its own fontFamily. Only the font changes; there is no background, because a PPTX run cannot have one. Markdown backticks read and write code runs."
},
"lang": {
"type": "string",
"pattern": "^[A-Za-z]{2,8}(-[A-Za-z0-9]{1,8})*$",
"description": "BCP-47 language tag of the run, such as 'fr-FR' or 'ja-JP', when it differs from the deck language. It sets the proofing language (PPTX a:rPr lang) and the language the run's script fonts and glyph variants follow (for example the Japanese or the Simplified Chinese face for Han characters); without it the run follows the deck language.",
"examples": [
"fr-FR",
"ja-JP",
"de"
]
},
"link": {
"type": "string",
"pattern": "^(https?://|mailto:|tel:)\\S+$",
"description": "URL to link the run text to: an http(s) URL, a 'mailto:' address or a 'tel:' number, without whitespace. The preview draws it as a link and PPTX export writes a native hyperlink for all three; any other scheme is not valid.",
"examples": [
"https://acme.com",
"https://acme.com/case-studies/beta",
"mailto:hello@acme.com",
"tel:+15551234567"
]
},
"superscript": {
"type": "boolean",
"description": "Whether the run is rendered as superscript."
},
"subscript": {
"type": "boolean",
"description": "Whether the run is rendered as subscript."
},
"cite": {
"oneOf": [
{
"type": "string",
"minLength": 1
},
{
"type": "array",
"minItems": 1,
"items": {
"type": "string",
"minLength": 1
}
}
],
"description": "One or more ids from the top-level references list that this run cites. Engines draw a superscript marker ('1', or '1,2' for several ids) directly after the run and list '<n> <reference text>' in the slide's footnote area; markers are numbered per deck in order of first use, and the same id keeps its number. An id missing from references is a validation error (cite-unknown-reference). Supported in text, bullets and list item runs, in the slide title, subtitle and tag, and in the quote text.",
"examples": [
"gartner-2026",
[
"gartner-2026",
"annual-report"
]
]
},
"footnote": {
"oneOf": [
{
"type": "string",
"minLength": 1
},
{
"type": "array",
"minItems": 1,
"items": {
"$ref": "#/$defs/TextRun"
}
}
],
"description": "An inline note for this run, without a references entry. Engines draw a superscript marker after the run and list the note in the slide's footnote area; every footnote takes a new number in the deck's marker sequence. Supported in text, bullets and list item runs, in the slide title, subtitle and tag, and in the quote text.",
"examples": [
"Excludes the discontinued hardware line."
]
}
}
}
]
}