Skip to main content
Every project has active settings — trim, background, subtitle style, layout — that control how exports are rendered. Use project settings when you want project-local overrides that aren’t worth bundling into a shared preset. See Render settings reference for the shared preset, settings.style, and settingsOverride field map.

client.projects.getSettings(projectId, options?)

Fetch a project’s active settings.

client.projects.updateSettings(projectId, body, options?)

Patch the active project settings. You can apply a preset, pass raw settings, or both (the preset is applied first, then settings overrides are merged on top).

Fields

string
Apply a reusable preset. Omit it to leave the current preset unchanged.
object
Patch applied on top of the preset. Use style for preset-shaped overrides, plus project-local fields such as displayLanguages, chordSettings, and duetSingerFilter.

Discovering valid fields

Convert the update schema to JSON Schema at runtime to discover every valid field:
Agents should call this before mutating project settings so they always know the current shape.

Common patterns

Project settings vs presets

What’s next