Skip to content
Coupon

Guitar Pro Tabs

Find it. Learn it. Play it.

Visitor offer

20% off Guitar Pro

Use our code at checkout where eligible.

View the coupon
Files, import, and migration 10 min read

Import ASCII or plain-text tab into Guitar Pro

Guitar Pro supports ASCII import, but plain-text tablature is a visual convention rather than a precise score format. Clean six aligned string lines first, import a short representative section, and expect to reconstruct rhythm and techniques after the pitches arrive.

A blank paper card beside six parallel wooden rods and a pencil

The practical answer

Treat ASCII import as a head start on string-and-fret entry, not as lossless conversion: preserve the source, clean its layout, then rebuild timing, barlines, tuning, and articulations against the recording.

A step-by-step approach

  1. 1

    Preserve and clean the text

    Duplicate the source, use a monospaced editor, and remove prose or chord lines that interrupt each tablature block.

  2. 2

    Standardise six-string blocks

    Align string labels, dashes, barlines, fret numbers, and multi-digit frets across complete top-to-bottom blocks.

  3. 3

    Import a representative passage

    Use File > Import > ASCII and first test a section containing chords, rests, multi-digit frets, and techniques.

  4. 4

    Rebuild musical structure

    Set tuning, key, metre, tempo, bars, note values, rests, ties, and voices against a trusted recording or score.

  5. 5

    Add techniques and verify

    Replace ambiguous text symbols with Guitar Pro articulations, check fingering, then compare every section by sight and sound.

Know what ASCII tab can and cannot represent

ASCII tab places fret numbers along text lines that stand for strings. It can communicate approximate order, chord shapes, string choice, and bar divisions when carefully aligned. Guitar Pro officially lists ASCII among its supported import formats.

There is no universal ASCII standard for exact duration, voices, tuplets, grace timing, repeats, dynamics, or techniques. Characters such as h, p, /, \, x, ~, and parentheses vary between authors. Horizontal spacing can suggest time, but proportional timing collapses when fonts, tabs, or multi-digit fret numbers shift.

Prepare a parser-friendly source

Work on a copy in a plain-text editor with a monospaced font. Keep each guitar block as six consecutive lines ordered consistently from high string to low string, with stable labels, dash characters, and vertical barlines. Remove commentary, lyrics, chord names, and counting lines that split those six lines.

Align simultaneous notes vertically and give 10, 11, and other multi-digit frets enough columns so later events stay aligned. Standardise line endings and plain ASCII punctuation when smart quotes or decorative Unicode characters appear. Preserve headings separately so useful section names are not lost.

Run a representative import first

Use File > Import > ASCII Tab and start with a short passage that exercises the source: one chord, one single-note run, a multi-digit fret, a barline, a rest-like gap, and at least one technique symbol. If those fail, revising the text pattern is faster than repairing an entire imported song.

Check string order and tuning immediately. A visually familiar shape can become the wrong pitch if the source uses drop tuning, seven strings, capo-relative numbers, or an unconventional line order. Set the destination instrument correctly before spending time on rhythm.

Reconstruct rhythm rather than trusting spaces

Set tempo, time signature, pickups, and bar boundaries from a reliable recording or published score. Enter note values and rests bar by bar, watching Guitar Pro’s duration checks. Use ties for sustained notes and another voice only when parts genuinely overlap independently.

A text row of evenly spaced numbers does not prove equal eighth notes, and a long run of dashes does not prove a measured rest. Count attacks against the recording, start with the rhythmic skeleton, then place the imported pitches onto that verified structure.

Translate techniques and proof every section

Replace ASCII hints with Guitar Pro’s explicit hammer-on, pull-off, slide, bend, vibrato, palm-mute, let-ring, dead-note, harmonic, accent, and grace-note tools. Decide what each symbol means from the source legend or recording instead of assuming one author’s slash or x convention.

Compare the finished passage at slow speed, inspect standard notation and tablature together, and verify chord attacks, sustains, repeats, endings, and section transitions. Keep the original text alongside the .gp file as provenance. If most rhythm and technique must be rebuilt, that is a limitation of the source format rather than a failed import.

Common questions

Yes. Guitar Pro officially supports ASCII import. Results depend on a consistent six-line text layout and still require musical verification.
Check line order, tuning, capo assumptions, string count, and alignment of multi-digit frets. Correct the destination instrument before rebuilding rhythm.
Do not rely on it. Plain-text spacing has no universal timing semantics and often changes with formatting. Reconstruct note values, rests, metre, and pickups from a trusted reference.
They often suggest hammer-ons, pull-offs, slides, dead notes, and vibrato, but conventions vary. Use the source legend or recording, then replace them with explicit Guitar Pro techniques.

Sources and review notes

Product details were checked against the official sources below on 10 August 2026. Offers and software details can change, so confirm current terms before buying.