Written by Daniel Murphy | Last updated: June 2026
How to Use This Page
This page covers the most common problems encountered when using GuitarChordIdentifier.com — including incorrect chord identifications from both input modes, failed microphone detection, unexpected inversion results, and mobile-specific issues. Work through the section that matches your situation. If your problem is not covered here, use the Contact page to submit a technical question.
For background on how both identification pipelines work and what accuracy to expect, see the How It Works page.
Fret Input Problems
Problem: The identified chord name seems completely wrong for the shape I entered.
The most common cause is an incorrect fret or string entry. A single wrong position — one fret too high, one string off — can produce an entirely different pitch class set and a completely different chord name. Before reporting a tool error, verify:
- Are all selected strings the ones actually ringing in your chord shape?
- Are muted strings (strings you are not playing) excluded from your selection?
- Is the fret number correct? Fret 0 = open string; fret 1 = the first fret from the nut; fret 2 = the second fret, and so on.
- Is the correct string selected? String 6 is the thickest low E; string 1 is the thinnest high E.
A particularly common error: accidentally including the open low E or open high E string when those strings are actually muted in the shape you are playing.
Problem: The tool identifies my chord as a seventh chord but I thought I was playing a simple triad.
Check whether any open strings are included in your selection that you did not intend. In many standard chord shapes, an adjacent open string can be accidentally selected. For example:
- An open C shape (x32010) includes the open B string (string 2) and the open high E string (string 1). If you accidentally include the open low E string (MIDI 40, pitch class E), the chord becomes an Em7 configuration rather than C major.
- An open G shape (320033) is a complete G major chord. If the open A string (string 5) is accidentally included, A is added to {G, B, D}, producing a possible G6 or Em7/G identification.
Review your string selections carefully and exclude any strings that are muted or not part of the intended chord.
Problem: The tool does not recognise my chord at all.
If no chord name is returned, the pitch class set you have entered does not match any chord in the current database. This can happen with:
- Very unusual voicings — highly extended chords (13th chords with omissions), altered chords, or experimental voicings with no standard name
- Only one or two notes selected — a minimum of three distinct pitch classes is required to identify a triad
- All notes on the same pitch class — for example, selecting multiple G notes across strings produces a single pitch class {G} with no intervals to analyse
If you believe the chord should be identifiable, use the Contact page to report it with the specific fret positions — Daniel will review whether the chord should be added to the database.
Problem: My chord has a capo and the identification is wrong.
The fret input mode is calibrated for standard tuning without a capo. With a capo on fret N, all open string pitches are raised by N semitones. A shape that produces G major in standard tuning with a capo on fret 2 actually produces A major. The tool does not currently adjust for capo position automatically — this is a documented feature limitation. To get the correct identification with a capo, enter the actual sounding fret positions (add the capo fret number to each of your relative fret positions) and use the open string MIDI values corresponding to the capo position.
Microphone Detection Problems
Problem: The microphone mode will not start.
The three most common causes:
- Another application is holding the microphone. Close all communication apps — Zoom, Teams, Discord — reload the page, and try again.
- Browser permission is blocked. To reset:
- Chrome: Lock icon in address bar → Site settings → Microphone → Allow
- Firefox: Lock icon → Connection secure → More information → Permissions → Use the Microphone → Allow
- Safari: Safari → Settings → Websites → Microphone → find guitarchordidentifier.com → Allow
- System-level microphone access is disabled.
- Windows: Settings → Privacy and Security → Microphone → ensure your browser is listed and allowed
- macOS: System Settings → Privacy and Security → Microphone → ensure your browser is ticked
Problem: The microphone mode detects no chord or returns a random result.
Guitar volume is too low. The guitar must be loud enough for the microphone to capture individual string fundamentals above the noise floor. For acoustic guitars, play with confident strumming rather than a light touch. For electric guitars, ensure the amplifier or audio interface output is at an appropriate level.
Excessive ambient noise. Background noise with energy in the guitar frequency range (80–1,200 Hz) competes directly with the guitar signal. Test in a quieter environment if possible.
String buzz or fret noise. String buzz generates additional frequencies that can produce false spectral peaks. Ensure your chord is fretted cleanly with firm finger pressure.
Microphone placed too far from the guitar. Move the microphone or built-in laptop microphone within 30–50 cm of the guitar soundhole or amp speaker for the strongest signal.
Problem: The microphone mode consistently identifies the wrong chord — not a random result, but a specific wrong name.
This is usually caused by the harmonic series filter misidentifying a harmonic as a separate fundamental. On guitar, the second harmonic (one octave up) of each string is often as loud as the fundamental. If the filter incorrectly treats the second harmonic of string 6 as a separate note, it adds a phantom pitch class that shifts the chord identification.
Common manifestation: A G major chord (G, B, D) being identified as Gmaj7 (G, B, D, F#) because the second harmonic of the B string (B4 → B5) is being partially interpreted as an independent note at a similar frequency to F#.
Fixes to try:
- Play the chord closer to the microphone to increase fundamental-to-harmonic ratio
- Use a cleaner pickup position (neck pickup rather than bridge, if applicable) — bridge pickups emphasise upper harmonics
- Avoid the distortion or overdrive channel — heavy saturation makes all harmonics equally loud and severely degrades polyphonic detection
Problem: Barre chords are identified less reliably than open chord shapes.
This is expected and documented. Barre chords produce a denser harmonic spectrum than open chord shapes because all notes are fretted strings with similar harmonic profiles — there is less acoustic differentiation between individual string fundamentals. Open chord shapes benefit from the distinct tonal character of open strings, which aids harmonic series separation in the detection pipeline. For critical identification of barre chord voicings, fret input mode is strongly recommended.
Inversion-Specific Problems
Problem: My chord is showing as an inversion (e.g. G/D) but I think it should be root position.
The inversion is determined by the lowest note detected or selected. If the detection pipeline identifies a low note as the bass that you intended to be muted, the result will show as an inversion. In fret input mode, verify that the lowest string in your selection is the root note you intend as the bass. In microphone mode, string buzz or sympathetic vibration on lower strings can introduce a bass note that shifts the inversion identification.
Mobile-Specific Problems
Problem: The fret input interface is difficult to use on a small screen.
The virtual fretboard is designed for desktop use. On mobile screens, individual fret positions can be difficult to tap accurately. Use the browser’s pinch-to-zoom feature to expand the fretboard area, or rotate your device to landscape orientation for a wider fretboard display. Desktop use is recommended for precise fret input.
Problem: Microphone chord detection does not work on my iPhone.
iOS Safari applies AudioContext restrictions that require a user tap to unlock before microphone capture begins. Tap the start button clearly and play the chord immediately after. iOS also applies additional audio processing that can affect polyphonic detection. For reliable guitar chord identification on iOS, fret input mode is recommended over microphone mode.
Still Having Problems?
If none of the above resolves your issue, the FAQ covers additional questions about result interpretation and detection accuracy. For problems not addressed in either page, contact Daniel Murphy directly via the Contact page with the following information:
- The input mode you were using (fret input or microphone)
- For fret input: the exact string and fret positions you entered
- For microphone mode: your browser, OS, guitar type (acoustic/electric/clean/distorted), and microphone type
- The chord result you received and what you expected
- Whether the problem is consistent or intermittent
Response time for technical issues: 24–48 hours.
Written by Daniel Murphy, founder of GuitarChordIdentifier.com. Last updated: June 2026.