What tuning is this tab in?

By machado001 · 19 September 2026

Open your tab file with Tabline

Why the fret numbers cannot tell you

Tablature is a map of positions, not of pitches. A number on a line means “press this fret on this string”, and what that position sounds like depends entirely on what the string is tuned to. Tune a string down a whole step and everything played on it sounds a whole step lower at exactly the same fret — the page does not change at all.

That is why a tab can look right and sound wrong. Standard notation has the opposite habit: it names pitches and says nothing about where your fingers go, which is exactly why reading tab and notation together closes the gap in each. The pair is also the fastest way to work out a tuning, and we will use it below.

Where the tuning lives in a Guitar Pro file

A .gp, .gp5 or .gpx file is not a picture of a tab. It is a structured score: notes, durations, strings, frets, tempo, instrument — and a tuning, held as a list of pitches, one per string. Crucially the tuning belongs to the track, not to the file. A score with a guitar, a bass and a second guitar can carry three different tunings, and in Guitar Pro itself the setting sits with the track rather than with the document — its own tutorials, as of September 2026, reach it through the track inspector. The five Guitar Pro extensions all store it; none of them makes it visible in the fret numbers.

Tabline reads that per-track list rather than assuming six strings: how many strings a track has is simply the length of its own tuning, and that is the number the app works from. A track whose tuning has no strings at all — a piano part, say — has no tablature to show, so the tab-only view is not offered for it.

How to tell what tuning this tab is in on a phone

1. Check which track you are looking at. A player has to choose one. Tabline opens on the first track that is not percussion, has at least six strings and carries a General MIDI guitar program; failing that, the first fretted track that is not percussion; failing that, the first track in the file. If the score has a bass or a second guitar, switch to it before drawing conclusions.
2. Count the lines of the tab staff. Six lines is a six-string tuning, seven lines a seven-string one. This alone rules a lot out.
3. Watch the notation staff while the open strings ring. Notation shows pitch, so an open sixth string drawn as D rather than E is a dropped sixth string. Guitar Pro has its own settings for how shifted tunings and capos are reflected on the notation staff, so treat this as strong evidence, not a certificate.
4. Read the note names on the fretboard. Tabline’s fretboard labels every dot with the pitch that note sounds, so an open string effectively names itself as the score plays. The fretboard is part of the one-time unlock; opening, reading and playback are free.

The tunings you will actually meet

Low string first, as tuner sites and instrument makers spell them in September 2026. Most tab archives are one of these five.

A file in half-step-down tuning is the quiet trap here: the fret numbers are identical to the standard-tuning version of the same song, the tab looks completely ordinary, and it will not match the recording until you drop your own strings a semitone.

Seven- and eight-string files

Extended-range scores give themselves away instantly, because the tab staff grows a line for every extra string. Seven-string files are usually a low B added under standard tuning; eight-string files are most often listed as F♯ B E A D G B E, though plenty of players tune that eighth string to a low E instead. Either way the file says what it is, and a player that reads the tuning will draw the extra lines rather than fold them into six.

Tabline builds its fretboard from the same number: seven strings in the file means seven strings on the neck. The neck itself covers frets 0 to 12 on a phone, and 0 to 15 where a tablet has the width for its two-pane layout, and a note played beyond the end of it is still named in the readout even though there is no dot for it — useful on the kind of score that lives at the fifteenth fret.

When the file’s tuning is simply wrong

Tab files are made by people, and the tuning is one more field they can get wrong. The classic case, argued out on guitar forums for years, is a song recorded in a dropped tuning transcribed into a file that claims standard tuning: the shapes are approximately right, the low notes are not, and everything on the sixth string is a couple of semitones out. The tell is that the rest of the arrangement matches the recording and one string does not.

There is no fixing that inside a player. Tabline is a player, not an editor — it will not retune a score, and it does not pretend the file says something it does not. What it will do is let you hear the file as written, at a speed where you can tell what is wrong: the slow-down-and-loop method is as good for auditioning a suspect bar as it is for learning one. From there you either retune to what the file wants, or find a better transcription.

What about MusicXML?

MusicXML carries whatever the exporting program wrote. A part exported as pitches only has no strings and no frets in it at all, so there is nothing for a tab staff to stand on, and you get notation. When the exporter did include the string and fret data, the tuning travels with it like any other part of the score. There is more on that in the guide to opening MusicXML and .mxl files on Android.

The short version

The tuning is a fact about the file, sitting on the track, invisible in the numbers. Count the strings, read the pitches, check you are on the right track, and a tab stops being a puzzle about what it wants your guitar to be.