Skip to content

Non-English songs for Musixmatch

Each convention keeps its source, language scope and the part that still needs judgment.

55 conventions · 18 related checks

The checks below catch specific patterns in your text. They support your review; passing them does not verify every part of a convention.

Generally use original scripts

All supported languages where applicable Musixmatch Lyrics Guidelines (opens in a new tab) Transcription, formatting, sync, structure, performers and translation. Verified 2026-09-16.

Generally use original scripts; consult the linked romanization guidance for details.

What LyricLint can establish

Retain original script; no automatic transliteration. See official supplemental sources below.

Transcribe D · MX-T08

The described translation feature is desktop-only

Contribution workflow All supported languages where applicable Musixmatch Lyrics Guidelines (opens in a new tab) Transcription, formatting, sync, structure, performers and translation. Verified 2026-09-16.

What LyricLint can establish

Native workflow limitation; local preservation is a separate capability.

Translate heading · MX-L01

Translate the existing formatted lines individually

All supported languages where applicable Musixmatch Lyrics Guidelines (opens in a new tab) Transcription, formatting, sync, structure, performers and translation. Verified 2026-09-16.

Translate the existing formatted lines individually; do not combine several source lines into one translation line.

What LyricLint can establish

Preserve known alignment metadata; no automatic translation. Japanese has a meaning-distribution qualification.

Translate A · MX-L02

Prefer verified, locked source lyrics to reduce later translation loss

Contribution workflow All supported languages where applicable Musixmatch Lyrics Guidelines (opens in a new tab) Transcription, formatting, sync, structure, performers and translation. Verified 2026-09-16.

What LyricLint can establish

Recommendation, not a text-validation error or a claim LyricLint can verify the lock.

Translate A · MX-L03

Transcription and formatting rules also apply to translations

All supported languages where applicable Musixmatch Lyrics Guidelines (opens in a new tab) Transcription, formatting, sync, structure, performers and translation. Verified 2026-09-16.

What LyricLint can establish

Track translation status explicitly; do not infer it from script/header vocabulary.

Translate B · MX-L04

Preserve the source line's tone

Needs contextual review All supported languages where applicable Musixmatch Lyrics Guidelines (opens in a new tab) Transcription, formatting, sync, structure, performers and translation. Verified 2026-09-16.

What LyricLint can establish

Human linguistic review.

Translate C · MX-L05

Retain words/names that cannot sensibly be translated

Needs contextual review All supported languages where applicable Musixmatch Lyrics Guidelines (opens in a new tab) Transcription, formatting, sync, structure, performers and translation. Verified 2026-09-16.

What LyricLint can establish

No automatic proper-name translation or normalization.

Translate D · MX-L06

Convey the intended message idiomatically instead of mechanically translating each word

Needs contextual review All supported languages where applicable Musixmatch Lyrics Guidelines (opens in a new tab) Transcription, formatting, sync, structure, performers and translation. Verified 2026-09-16.

What LyricLint can establish

Outside deterministic format conversion.

Translate E · MX-L07

Seek help/research instead of leaving blanks or question-mark replacement tokens for undeciphered words

Partly checked from text English English FAQ (opens in a new tab) Official Musixmatch Help Center guidance. Verified 2026-09-16.

What LyricLint can establish

Direct conflict with Genius [?] for English. Keep the uncertainty visible as unresolved work; neither delete the token nor invent a word.

Checks for this convention

  • A word still needing transcription
    English FAQ (opens in a new tab) Official Musixmatch Help Center guidance. Verified 2026-09-16.
    Requires review under this check
    We hear [?] tonight

    The English Musixmatch FAQ rejects question-mark replacement tokens. Keep this uncertainty visible until listening or research establishes the word; deleting the token or inventing lyrics would lose information.

    Accepted by this check
    We hear rain tonight

    A word still needing transcription , with trigger and fix details

FAQ, unclear lyrics · MX-EN01

Ask for confirmation of unlisted abbreviated forms

Needs contextual review English English FAQ (opens in a new tab) Official Musixmatch Help Center guidance. Verified 2026-09-16.

What LyricLint can establish

A deterministic engine can report missing coverage, not invent an approved spelling or contact a contributor.

FAQ, abbreviations · MX-EN02

Secondary vocals use parentheses and generally lowercase beginnings unless grammar or sentence-ending punctuation calls for capitals

Partly checked from text English English FAQ (opens in a new tab) Official Musixmatch Help Center guidance. Verified 2026-09-16.

What LyricLint can establish

Ordinary vocalizations and grammatical openings such as Whatever lowercase within a lead line when converting Genius wording, and offer a preview correction for native Musixmatch wording. Names, English I, sentence punctuation and uncertain vocal roles retain contextual review.

Checks for this convention

  • Capitalized backing vocals
    Flagged example
    We return (Yeah)

    Ordinary English backing-vocal openings use lowercase inside a lyric line. Pronouns, names and new sentences keep their grammatical capitals.

    Accepted by this check
    We return (yeah)

    Fix: Lowercase “Yeah”

    Capitalized backing vocals , with trigger and fix details

FAQ, backing vocals · MX-EN03

Align the first sound without a lead-in

Contribution workflow English English FAQ (opens in a new tab) Official Musixmatch Help Center guidance. Verified 2026-09-16.

Align the first sound without a lead-in; include live speech and remix vocals unless effects make them genuinely indecipherable; listen to the entire track before marking it instrumental.

What LyricLint can establish

Authoritative workflow qualification, not proof that current anchors are accurate or that a long opening means an instrumental track.

FAQ, sync/remixes/live · MX-EN04

Supplies brand spellings and context-dependent short names

Needs contextual review English English Insights (opens in a new tab) Official Musixmatch Help Center guidance. Verified 2026-09-16.

What LyricLint can establish

Curated identity evidence; do not expand every nickname or treat brand recognition as certain.

Insights, Brand Love · MX-EN05

Supplies British, Nigerian, Patois and contemporary slang with meanings and allowed variants

Needs contextual review English English Insights (opens in a new tab) Official Musixmatch Help Center guidance. Verified 2026-09-16.

What LyricLint can establish

These are separate lexical inventories; translating dialect into standard English is not a correction. A token's meaning still matters.

Insights, regional/slang tables · MX-EN06

Preserve the dialect actually sung instead of standardizing an original transcription to Bokmål/Nynorsk

Needs contextual review Norwegian Norwegian Insights (opens in a new tab) Official Musixmatch Help Center guidance. Verified 2026-09-16.

What LyricLint can establish

Existing Genius-mode dictionary checks are narrow language curation; never use them to erase sung Norwegian dialect in MXM. Artist origin is suggested human research, not an automatic dialect classifier.

Dialektbruk · MX-NO01

Use normal Norwegian proper-name/acronym case and the company's/product's actual casing

Needs contextual review Norwegian Norwegian Insights (opens in a new tab) Official Musixmatch Help Center guidance. Verified 2026-09-16.

What LyricLint can establish

Does not expressly revoke the main line-initial rule. Preserve names such as mixed-case brands; do not blanket-case tokens.

Stor forbokstav · MX-NO02

Prefer Bokmål for translations into Norwegian

Needs contextual review Norwegian Norwegian Insights (opens in a new tab) Official Musixmatch Help Center guidance. Verified 2026-09-16.

Prefer Bokmål for translations into Norwegian; compound translations normally join, with hyphens for certain long/readability cases.

What LyricLint can establish

The Bokmål preference is translation-specific, not authorization to normalize original dialect lyrics. Compound analysis needs language context.

Translation / compounds · MX-NO03

Sámi is a separate language whose writing must be retained

Unresolved source scope Norwegian Norwegian Insights (opens in a new tab) Official Musixmatch Help Center guidance. Verified 2026-09-16.

Sámi is a separate language whose writing must be retained; knowledgeable transcription is needed. Lyricless joik is described as instrumental.

Guidelines disagree. The official sources behind this convention state different requirements. LyricLint preserves your wording and lists each source above rather than choosing one for you.

What LyricLint can establish

Do not map Sámi into Norwegian or remove vocables by heuristic. The joik reference to #INSTRUMENTAL needs reconciliation with the main interior-only marker rule and track-level instrumental workflow.

Samisk og joiking · MX-NO04

English nouns embedded in German use noun capitals

Needs contextual review German German Insights (opens in a new tab) Official Musixmatch Help Center guidance. Verified 2026-09-16.

English nouns embedded in German use noun capitals; English clauses retain English grammar; borrowed verbs/adjectives remain lowercase; specified adjective+noun combinations capitalize both.

What LyricLint can establish

Token-level “English-looking word” detection cannot choose the rule. Existing Genius title-case diagnostics are not a German grammar engine.

English-word casing · MX-DE01

A curated elision table depends on actual sung pronunciation and explicitly allows alternatives in several entries, including apostrophized/non-apostrophized forms

Needs contextual review German German Insights (opens in a new tab) Official Musixmatch Help Center guidance. Verified 2026-09-16.

What LyricLint can establish

Encode allowed sets and scope, not a single canonical rewrite. Absence from a supplemental table cannot prohibit an official allowed form.

Apostrophes · MX-DE02

Audible producer tags are lyrics

Needs contextual review German German Insights (opens in a new tab) Official Musixmatch Help Center guidance. Verified 2026-09-16.

Audible producer tags are lyrics; a recognition list is supplied.

What LyricLint can establish

Broad agreement on preserving vocals. A list of known tags never authorizes insertion of an unheard tag.

Producer tags · MX-DE03

Dialect-shortened words can be independent words without elision apostrophes

Needs contextual review German German Insights (opens in a new tab) Official Musixmatch Help Center guidance. Verified 2026-09-16.

Dialect-shortened words can be independent words without elision apostrophes; contractions of separate words use apostrophes.

What LyricLint can establish

Do not “repair” every shortened German dialect token as omitted Standard German letters.

Dialects · MX-DE04

Terminal punctuation is limited to necessary question/exclamation marks and closing parentheses/quotes. Hyphens mark incomplete words

Partly checked from text Spanish Spanish Insights (opens in a new tab) Official Musixmatch Help Center guidance. Verified 2026-09-16.

Terminal punctuation is limited to necessary question/exclamation marks and closing parentheses/quotes. Hyphens mark incomplete words; ellipses mark incomplete sentences, not ordinary performance pauses.

What LyricLint can establish

Review interruption/phrase context; do not strip closing syntax or infer ellipses from pauses.

Checks for this convention

  • Terminal punctuation needing review
    Musixmatch Lyrics Guidelines (opens in a new tab) Transcription, formatting, sync, structure, performers and translation. Verified 2026-09-16.
    Flagged example
    We return.

    Musixmatch excludes commas and non-acronym periods at lyric line endings. Acronyms retain their own punctuation; review names and abbreviations before removal.

    Accepted by this check
    We return

    Fix: Remove the period

    Terminal punctuation needing review , with trigger and fix details

  • An unconfirmed interruption
    Musixmatch Lyrics Guidelines (opens in a new tab) Transcription, formatting, sync, structure, performers and translation. Verified 2026-09-16.
    Requires review under this check
    If we could—

    Musixmatch uses a hyphen for an unfinished word and an ellipsis for an unfinished sentence or fade-out. A musical pause alone does not establish either; a Genius dropped-word dash cannot be rewritten from shape alone.

    Accepted by this check
    If we could return

    An unconfirmed interruption , with trigger and fix details

Insights, punctuation · MX-ES01

A shortened single word generally omits the apostrophe unless it distinguishes another real word

Needs contextual review Spanish Spanish Insights (opens in a new tab) Official Musixmatch Help Center guidance. Verified 2026-09-16.

A shortened single word generally omits the apostrophe unless it distinguishes another real word; merged-word contractions use an apostrophe; established colloquial abbreviations can be exceptions.

What LyricLint can establish

Genius's general omission-apostrophe guidance cannot be applied as an unconditional Spanish MXM rule.

Insights, elision/contractions · MX-ES02

Normal accents remain

Needs contextual review Spanish Spanish Insights (opens in a new tab) Official Musixmatch Help Center guidance. Verified 2026-09-16.

Normal accents remain; an apostrophe does not replace an accent. Retain original s/z if aspiration/substitution is audible, omitting only when entirely absent.

What LyricLint can establish

Accent checks can be scoped; phonetic presence requires listening.

Insights, spelling · MX-ES03

Actual direct speech uses colon + space + opening quote + capital. Omit the colon if it would end a line. Quotation may span lines. Indirect speech has no colon/quotes

Partly checked from text Spanish Spanish Insights (opens in a new tab) Official Musixmatch Help Center guidance. Verified 2026-09-16.

Actual direct speech uses colon + space + opening quote + capital. Omit the colon if it would end a line. Quotation may span lines. Indirect speech has no colon/quotes; hypothetical quoted words keep quotes but receive no colon or automatic initial capital.

What LyricLint can establish

Explicit conflict with MX-F13's comma. Review and encode the Spanish exception; do not apply a global quote-prefix transform.

Checks for this convention

  • A quotation with unconfirmed meaning
    Requires review under this check
    Dije, "Vuelve"

    Spanish direct speech uses a colon, a space and an opening quotation mark, except when the colon would end a line. Indirect speech and hypothetical words differ; quoted artist, song or album names are not necessarily speech.

    Accepted by this check
    Dije que vuelve

    A quotation with unconfirmed meaning , with trigger and fix details

Insights, direct speech · MX-ES04

Lead normally opens the line and determines sync

Needs contextual review Spanish Spanish Insights (opens in a new tab) Official Musixmatch Help Center guidance. Verified 2026-09-16.

Lead normally opens the line and determines sync; sequential secondary lyrics are plain, overlapping/background lyrics parenthesized. Unison/harmony is written once; echoes/reverb/nonhuman effects are excluded. In live performances, a lead's audience-directed aside takes parentheses unless alone on its line. Audience vocals are plain when carrying lyrics or standing alone, otherwise follow background treatment.

What LyricLint can establish

Role/overlap/effect classification needs audio or supplied facts. Performer identity alone does not decide role; text similarity does not prove an echo or simultaneous unison.

Insights, vocal roles · MX-ES05

Put secondary text midline only where a lead pause accommodates it, otherwise favor line end. Avoid initial parentheses

Partly checked from text Spanish Spanish Insights (opens in a new tab) Official Musixmatch Help Center guidance. Verified 2026-09-16.

Put secondary text midline only where a lead pause accommodates it, otherwise favor line end. Avoid initial parentheses; remove them when they enclose an entire line. No punctuation immediately before an opening parenthesis.

What LyricLint can establish

Structural edits can change timing and vocal attachment; require role/placement evidence. No unconditional “move all parentheses” conversion.

Checks for this convention

  • Spanish backing-vocal placement
    Spanish Insights (opens in a new tab) Official Musixmatch Help Center guidance. Verified 2026-09-16.
    Requires review under this check
    (Vuelve aquí)

    Spanish guidance avoids initial or whole-line backing parentheses and punctuation immediately before them. Confirm lead, background, audience and overlapping roles before moving or unwrapping text; the change can affect timing.

    Accepted by this check
    Vuelve (aquí)

    Spanish backing-vocal placement , with trigger and fix details

Insights, backing placement · MX-ES06

Normally lowercase openings, with grammatical/name and sentence-ending-punctuation exceptions

Partly checked from text Spanish Spanish Insights (opens in a new tab) Official Musixmatch Help Center guidance. Verified 2026-09-16.

What LyricLint can establish

Confirmed conflict with Genius's capital-initial ad-lib convention; grammar remains a precondition.

Checks for this convention

  • Capitalized backing vocals
    Flagged example
    We return (Yeah)

    Ordinary English backing-vocal openings use lowercase inside a lyric line. Pronouns, names and new sentences keep their grammatical capitals.

    Accepted by this check
    We return (yeah)

    Fix: Lowercase “Yeah”

    Capitalized backing vocals , with trigger and fix details

Insights, parenthetical case · MX-ES07

Acronyms use uppercase without separating dots/spaces

Partly checked from text Spanish Spanish FAQ (opens in a new tab) Official Musixmatch Help Center guidance. Verified 2026-09-16.

Acronyms use uppercase without separating dots/spaces; laughter units use commas.

What LyricLint can establish

Do not infer acronym or laughter role from arbitrary letters.

Checks for this convention

  • A possible Spanish acronym
    Spanish FAQ (opens in a new tab) Official Musixmatch Help Center guidance. Verified 2026-09-16.
    Requires review under this check
    Canto U.S.A.

    The Spanish FAQ writes acronyms in capitals without separating dots or spaces. Sung individual letters, abbreviations and names are different cases; their role cannot be inferred from punctuation alone.

    Accepted by this check
    Canto USA

    A possible Spanish acronym , with trigger and fix details

FAQ, acronyms/laughter · MX-ES08

Context can justify words above ten

Partly checked from text Spanish Spanish FAQ (opens in a new tab) Official Musixmatch Help Center guidance. Verified 2026-09-16.

Context can justify words above ten; the source illustrates a large quantity without a complete exception predicate.

What LyricLint can establish

The generic >10 conversion is not unconditional. Review fixed/contextual expressions and large values.

Checks for this convention

  • A number without established context
    Musixmatch Lyrics Guidelines (opens in a new tab) Transcription, formatting, sync, structure, performers and translation. Verified 2026-09-16.
    Requires review under this check
    Twenty-one stars

    Musixmatch generally spells quantities through ten and uses digits above ten, with separate rules for dates, phones, decades, names, fixed expressions and times. Exact times and o’clock differ. A value alone does not prove its role or pronunciation; no numeric rewrite is offered.

    Accepted by this check
    At dawn

    A number without established context , with trigger and fix details

FAQ, numbers · MX-ES09

Preserve artist/band spelling/case

Needs contextual review Spanish Spanish FAQ (opens in a new tab) Official Musixmatch Help Center guidance. Verified 2026-09-16.

Preserve artist/band spelling/case; detailed grammar distinguishes names, religion, geography, celestial objects, titles, dates and ordinary nouns. Mentioned artist, song and album names may be quoted.

What LyricLint can establish

No generic proper-name normalization. Direct speech is not the only permitted quotation role. The current Genius Spanish dictionary rules cover only a small subset.

FAQ, names/case · MX-ES10

Contains contextual homophone distinctions and explicit accent conventions, including unaccented solo and specified demonstratives/short verb forms

Partly checked from text Spanish Spanish FAQ (opens in a new tab) Official Musixmatch Help Center guidance. Verified 2026-09-16.

What LyricLint can establish

Record source-specific lexical cases; not a general accent-removal operation. Meaning-dependent pairs remain review.

Checks for this convention

  • A source-specific Spanish accent
    Spanish FAQ (opens in a new tab) Official Musixmatch Help Center guidance. Verified 2026-09-16.
    Flagged example
    Sólo canto aquí

    The Musixmatch Spanish FAQ uses these specified words without a written accent. Check quoted names or embedded-language text before changing the form; this is not a general accent-removal rule.

    Accepted by this check
    Solo canto aquí

    Fix: Use Solo

    A source-specific Spanish accent , with trigger and fix details

FAQ, spelling/accents · MX-ES11

At most 70 characters per lyric line and ten lines per stanza

Partly checked from text Spanish Spanish FAQ (opens in a new tab) Official Musixmatch Help Center guidance. Verified 2026-09-16.

What LyricLint can establish

Adds a limit missing from the main plan. Unicode counting unit and stanza/tag relationship are unspecified; review the count definition before enforcement and never auto-split at character 70.

Checks for this convention

  • A long Spanish lyric line
    Spanish FAQ (opens in a new tab) Official Musixmatch Help Center guidance. Verified 2026-09-16.
    Requires review under this check
    Volvemos al camino donde cantan los recuerdos y nos esperan las voces del viento

    The Spanish FAQ limits lines to 70 characters but does not define the Unicode counting unit. This line has 80 UTF-16 units and 80 Unicode code points. Review musical phrasing and the count; do not split automatically at an arbitrary position.

    Accepted by this check
    Volvemos al camino
    Donde nos esperan las voces del viento

    A long Spanish lyric line , with trigger and fix details

  • More than ten lines in a lyric block
    Musixmatch Lyrics Guidelines (opens in a new tab) Transcription, formatting, sync, structure, performers and translation. Verified 2026-09-16.
    Flagged example
    Here we sing
    Here we stand
    Here we turn
    Here we rest
    Here we dream
    Here we wait
    Here we dance
    Here we stay
    Here we walk
    Here we rise
    Here we return

    Musixmatch limits formatted sections to ten physical lyric lines. Choose a break that follows the music and meaning; soft wraps are not extra lines, and a layout break does not establish a new musical tag.

    Accepted by this check
    Here we sing
    Here we stand
    
    Here we turn

    More than ten lines in a lyric block , with trigger and fix details

FAQ, line breaks · MX-ES12

Commas follow grammatical lists/appositions/vocatives, not every audible pause

Needs contextual review French French Insights (opens in a new tab) Official Musixmatch Help Center guidance. Verified 2026-09-16.

Commas follow grammatical lists/appositions/vocatives, not every audible pause; coordination has specific exceptions.

What LyricLint can establish

Grammar/audio timing are different inputs; no pause-based comma insertion.

Insights, punctuation · MX-FR01

Exclamation marks, colons and semicolons are prohibited, with an exception for punctuation belonging to a sung song title

Partly checked from text French French Insights (opens in a new tab) Official Musixmatch Help Center guidance. Verified 2026-09-16.

What LyricLint can establish

Conflicts with general MXM allowance and Genius's excitement-based exclamation convention. Scope the reviewed French rule and name exception explicitly.

Checks for this convention

  • Restricted French punctuation
    French Insights (opens in a new tab) Official Musixmatch Help Center guidance. Verified 2026-09-16.
    Requires review under this check
    Reviens!

    French Musixmatch guidance excludes exclamation marks, colons and semicolons, except punctuation that belongs to a sung song title. Preserve title punctuation; a text-only check cannot establish that exception.

    Accepted by this check
    Reviens

    Restricted French punctuation , with trigger and fix details

Insights, forbidden marks · MX-FR02

Required question marks have no preceding space, for grammatical questions or clearly questioning delivery

Partly checked from text French French Insights (opens in a new tab) Official Musixmatch Help Center guidance. Verified 2026-09-16.

What LyricLint can establish

Specific typography rule, not a blanket import of ordinary French publishing spacing. Delivery still needs judgment.

Checks for this convention

  • A space before a French question mark
    French Insights (opens in a new tab) Official Musixmatch Help Center guidance. Verified 2026-09-16.
    Flagged example
    Tu reviens ?

    The French Musixmatch article specifically places a question mark without a preceding space. This lyric convention differs from some ordinary French publishing typography.

    Accepted by this check
    Tu reviens?

    Fix: Remove the space

    A space before a French question mark , with trigger and fix details

Insights, questions · MX-FR03

Mark beginning/end elisions with apostrophes

Needs contextual review French French Insights (opens in a new tab) Official Musixmatch Help Center guidance. Verified 2026-09-16.

Mark beginning/end elisions with apostrophes; retain standard spelling for internal elisions.

What LyricLint can establish

Do not share an unconstrained Genius/English apostrophe inserter.

Insights, elision · MX-FR04

Join imperatives and pronouns with hyphens

Needs contextual review French French Insights (opens in a new tab) Official Musixmatch Help Center guidance. Verified 2026-09-16.

Join imperatives and pronouns with hyphens; verlan retains underlying spelling and hyphenates rearranged syllables.

What LyricLint can establish

Needs grammatical/lexical interpretation; no arbitrary syllable splitting.

Insights, imperatives/verlan · MX-FR05

The prose spells sub-ten or “precise” times, but its examples also use numeric times with minutes. Exactly ten is not specified

Unresolved source scope French French Insights (opens in a new tab) Official Musixmatch Help Center guidance. Verified 2026-09-16.

Guidelines disagree. The official sources behind this convention state different requirements. LyricLint preserves your wording and lists each source above rather than choosing one for you.

What LyricLint can establish

Internally ambiguous source: retain wording and block automatic boundary decisions until clarified.

Checks for this convention

  • A number without established context
    Musixmatch Lyrics Guidelines (opens in a new tab) Transcription, formatting, sync, structure, performers and translation. Verified 2026-09-16.
    Requires review under this check
    Twenty-one stars

    Musixmatch generally spells quantities through ten and uses digits above ten, with separate rules for dates, phones, decades, names, fixed expressions and times. Exact times and o’clock differ. A value alone does not prove its role or pronunciation; no numeric rewrite is offered.

    Accepted by this check
    At dawn

    A number without established context , with trigger and fix details

Insights, times · MX-FR06

y a has no apostrophe

Partly checked from text French French FAQ (opens in a new tab) Official Musixmatch Help Center guidance. Verified 2026-09-16.

y a has no apostrophe; French decade expressions and embedded English decade expressions have different constructions.

What LyricLint can establish

Explicit language scope, including mixed-language spans; no global decade-apostrophe rewrite.

Checks for this convention

  • An apostrophe in the French y a form
    French FAQ (opens in a new tab) Official Musixmatch Help Center guidance. Verified 2026-09-16.
    Flagged example
    Y'a du vent

    The French Musixmatch FAQ writes this spoken form as y a, without an apostrophe. Preserve unrelated quoted names or embedded languages.

    Accepted by this check
    Y a du vent

    Fix: Use y a

    An apostrophe in the French y a form , with trigger and fix details

FAQ, elision/decades · MX-FR07

Above-ten quantities normally use digits, but fixed expressions stay in words

Partly checked from text French French FAQ (opens in a new tab) Official Musixmatch Help Center guidance. Verified 2026-09-16.

What LyricLint can establish

Numeric interpretation must exclude fixed expressions; no blanket >10 conversion.

Checks for this convention

  • A number without established context
    Musixmatch Lyrics Guidelines (opens in a new tab) Transcription, formatting, sync, structure, performers and translation. Verified 2026-09-16.
    Requires review under this check
    Twenty-one stars

    Musixmatch generally spells quantities through ten and uses digits above ten, with separate rules for dates, phones, decades, names, fixed expressions and times. Exact times and o’clock differ. A value alone does not prove its role or pronunciation; no numeric rewrite is offered.

    Accepted by this check
    At dawn

    A number without established context , with trigger and fix details

FAQ, numbers · MX-FR08

Avoid disruptive midphrase backing/echo placement

Needs contextual review French French FAQ (opens in a new tab) Official Musixmatch Help Center guidance. Verified 2026-09-16.

Avoid disruptive midphrase backing/echo placement; significant backing material can appear at line end or separately.

What LyricLint can establish

Does not provide a reliable text-only echo-deletion predicate. Preserve until role/placement is established.

FAQ, backing vocals · MX-FR09

Use original Japanese script even when release metadata is romanized

Needs contextual review Japanese

Use original Japanese script even when release metadata is romanized; do not add furigana/readings, including unusual readings. Artist-selected kanji matter; use Japanese glyph forms rather than Chinese variants.

What LyricLint can establish

Header-English policy on Genius is unrelated. Distinguish pronunciation glosses from actual backing vocals before any removal; no global Han-character normalization.

Insights script sections; FAQ 3–5 · MX-JA01

Structure belongs in tagging. Explicit A-melody/pre-chorus/chorus labels have stated mappings

Japanese

Structure belongs in tagging. Explicit A-melody/pre-chorus/chorus labels have stated mappings; B-melody, solo and C-melody labels each allow more than one target. Intro/outro refer to sung sections, not pure instrumental edges.

What LyricLint can establish

Some explicit source labels support mapping; ambiguous labels require choice. Preserve source labels and musical identity.

Insights structure; FAQ 6 · MX-JA02

Halfwidth spacing/commas can aid phrasing and readability

Needs contextual review Japanese Japanese FAQ (opens in a new tab) Official Musixmatch Help Center guidance. Verified 2026-09-16.

Halfwidth spacing/commas can aid phrasing and readability; line breaks follow meaning and singability.

What LyricLint can establish

No automatic spacing at every script boundary or split at a fixed character count.

FAQ 1, 9 · MX-JA03

Vocalization spelling and Katakana/Latin choice depend on pronunciation, ordinary usage and official lyrics

Needs contextual review Japanese Japanese FAQ (opens in a new tab) Official Musixmatch Help Center guidance. Verified 2026-09-16.

Vocalization spelling and Katakana/Latin choice depend on pronunciation, ordinary usage and official lyrics; repeated vocables can use hyphens/spaces/line breaks by phrasing.

What LyricLint can establish

No universal romanization/interjection replacement or separator.

FAQ 2, 11, 13 · MX-JA04

Separate blocks with blank lines, but says a blank is not needed immediately after #INSTRUMENTAL

Unresolved source scope Japanese Japanese FAQ (opens in a new tab) Official Musixmatch Help Center guidance. Verified 2026-09-16.

Guidelines disagree. The official sources behind this convention state different requirements. LyricLint preserves your wording and lists each source above rather than choosing one for you.

What LyricLint can establish

Directly conflicts with MX-S12 requiring that blank. Do not silently select an automatic spacing policy.

Checks for this convention

  • An instrumental interval needing review
    Musixmatch Lyrics Guidelines (opens in a new tab) Transcription, formatting, sync, structure, performers and translation. Verified 2026-09-16.
    Requires review under this check
    We sing
    
    #INSTRUMENTAL
    
    We return

    Musixmatch uses this marker only for more than fifteen consecutive seconds without qualifying lyrics between separately tagged sections, never inside a section or at a track edge. Whole-track instrumental status is separate. Text or two lyric-start times cannot prove the interval.

    Accepted by this check
    We sing
    
    We return

    An instrumental interval needing review , with trigger and fix details

FAQ 7 · MX-JA05

Lists Latin line starts, proper nouns/acronyms and parenthetical beginnings among capitalization cases

Unresolved source scope Japanese Japanese FAQ (opens in a new tab) Official Musixmatch Help Center guidance. Verified 2026-09-16.

Lists Latin line starts, proper nouns/acronyms and parenthetical beginnings among capitalization cases; rejects arbitrary all-caps/all-lowercase/title-case presentation.

Guidelines disagree. The official sources behind this convention state different requirements. LyricLint preserves your wording and lists each source above rather than choosing one for you.

What LyricLint can establish

Parenthetical wording differs from main grammatical-only guidance; exact mixed-script/parenthetical scope needs resolution.

Checks for this convention

  • Capitalized backing vocals
    Flagged example
    We return (Yeah)

    Ordinary English backing-vocal openings use lowercase inside a lyric line. Pronouns, names and new sentences keep their grammatical capitals.

    Accepted by this check
    We return (yeah)

    Fix: Lowercase “Yeah”

    Capitalized backing vocals , with trigger and fix details

  • A lowercase line beginning
    Musixmatch Lyrics Guidelines (opens in a new tab) Transcription, formatting, sync, structure, performers and translation. Verified 2026-09-16.
    Flagged example
    we return

    Musixmatch capitalizes lyric line beginnings. Preserve established name casing and review mixed-language context before changing it.

    Accepted by this check
    We return

    Fix: Capitalize w

    A lowercase line beginning , with trigger and fix details

  • Expressive capitals needing review
    Musixmatch Lyrics Guidelines (opens in a new tab) Transcription, formatting, sync, structure, performers and translation. Verified 2026-09-16.
    Requires review under this check
    WE RETURN AGAIN

    Musixmatch does not use all-caps for shouting or arbitrary title case. Names, acronyms, German nouns and embedded languages require context; no automatic lowercasing is offered.

    Accepted by this check
    We return again

    Expressive capitals needing review , with trigger and fix details

FAQ 8 · MX-JA06

Children's lyric kanji/kana choices depend on intended age

Needs contextual review Japanese Japanese FAQ (opens in a new tab) Official Musixmatch Help Center guidance. Verified 2026-09-16.

What LyricLint can establish

Audience metadata/human judgment; no universal all-kana conversion.

FAQ 10 · MX-JA07

Avoid excessive Japanese corner quotes in dialogue

Needs contextual review Japanese Japanese FAQ (opens in a new tab) Official Musixmatch Help Center guidance. Verified 2026-09-16.

Avoid excessive Japanese corner quotes in dialogue; line breaks/halfwidth spaces/parentheses can support long spoken content.

What LyricLint can establish

General comma-plus-quotes treatment is not a universal Japanese conversion.

FAQ 12 · MX-JA08

Use fullwidth question/exclamation marks after fullwidth preceding characters, ASCII forms after halfwidth characters

Partly checked from text Japanese Japanese FAQ (opens in a new tab) Official Musixmatch Help Center guidance. Verified 2026-09-16.

What LyricLint can establish

Define and review width classification for mixed scripts and punctuation; no NFKC normalization of the whole draft.

Checks for this convention

  • A Japanese punctuation width mismatch
    Japanese FAQ (opens in a new tab) Official Musixmatch Help Center guidance. Verified 2026-09-16.
    Flagged example
    帰る?

    The Japanese Musixmatch FAQ uses fullwidth question and exclamation marks after fullwidth characters and ASCII marks after halfwidth characters. Only this mark changes; lyric scripts and other character forms stay exact.

    Accepted by this check
    帰る?

    Fix: Use ?

    A Japanese punctuation width mismatch , with trigger and fix details

FAQ 14 · MX-JA09

Where strict sentence alignment fails, meaning may be redistributed over its existing two or three lines while total line count stays fixed

Japanese

What LyricLint can establish

Qualifies the main translation instruction. Preserve translation alignment; linguistic translation remains outside the transformer.

Insights, translations · MX-JA10

Native-script lyrics and romanized forms in the Translation surface are distinct. Editing automatic romanizations is restricted to high-rank Curators. The current article gives no usable complete per-language romanization list

All supported languages where applicable Romanization and supported languages (opens in a new tab) Official Musixmatch Help Center guidance. Verified 2026-09-16.

What LyricLint can establish

Preserve content kind and script. Do not claim that Arabic/Korean automatic romanization is available from this page title.

Romanization guidance · MX-W01

Translation must be personally authored, not copied or machine-translated, with context and original untranslatable terms preserved

Contribution workflow All supported languages where applicable How to translate (opens in a new tab) Official Musixmatch Help Center guidance. Verified 2026-09-16.

What LyricLint can establish

Document scope; the deterministic format engine does not translate lyrics.

Translation help · MX-W03