LoTW has confirmed over a billion QSO records since its launch. It's free. It's the gold standard for DXCC, WAS, VUCC, and WAZ credit. And yet every week, somebody posts on r/amateurradio asking why they can't get it working.
Here's the thing. LoTW isn't complicated. It's just poorly explained by the official documentation, which reads like it was written by committee in 2003 (because it was). This guide walks you through the full setup, from zero to your first confirmed QSO.
What LoTW Actually Does
Logbook of the World is a QSO matching service. You upload your log. The other station uploads theirs. If both logs agree on callsign, band, mode, date, and time (within a 30-minute window), LoTW marks that QSO as confirmed.
Those confirmations count toward ARRL awards: DXCC, WAS (Worked All States), VUCC (VHF/UHF Century Club), and WPX. No more mailing QSL cards to the ARRL incoming bureau and waiting 18 months.
LoTW is NOT a general-purpose logging program. You still need logging software (Log4OM, N1MM+, Ham Radio Deluxe, etc.) to create your ADIF files, which you then upload to LoTW.
Step 1: Request Your Certificate
LoTW uses a digital certificate system to verify that uploads really came from the claimed callsign holder. This is the part that trips people up.
- Download TQSL from https://lotw.arrl.org/lotw-help/installation/
- Install it. Run it.
- Go to Callsign Certificates → Request New Callsign Certificate
- Enter your callsign, your DXCC entity (United States for US hams), QSO start date (when you first operated under this call), and your mailing address exactly as it appears in the FCC ULS database.
That last point is where 40% of rejections happen. If your FCC address says "123 N Main St" don't type "123 North Main Street". Match it character for character.
After submitting, ARRL mails a postcard to your FCC address with a verification code. Not email. Physical mail. This takes 5-10 business days in the US, longer internationally.
Step 2: Load the Certificate
When your postcard arrives (or verification email, if you've used LoTW before and are adding a new call), you'll get a .tq6 file or a password to unlock your pending certificate.
In TQSL:
- Go to File → Load Certificate File if you received a .tq6
- Or go to Callsign Certificates, right-click your pending certificate, and enter the verification code
Once loaded, your certificate shows a green checkmark. You're in business.
Back up your certificate immediately. Go to Callsign Certificates → right-click → Save Callsign Certificate. Store the .p12 file somewhere safe. If you lose this and haven't backed it up, you'll need to request a new one from scratch. I've watched three different club members go through this pain. Don't be them.
Step 3: Set Up Your Station Location
TQSL needs a station location defined before you can sign and upload logs. This tells LoTW your grid square, CQ zone, and ITU zone.
- Click Station Locations in TQSL
- Add a new location
- Select your callsign certificate
- Fill in:
- DXCC Entity: United States (or your country)
- State/Province: your state
- Grid Square: your 6-character Maidenhead locator (use qthlocator.free.fr if you don't know yours)
- CQ Zone: 3, 4, or 5 for continental US
- ITU Zone: 6, 7, or 8 for continental US
- Name this location something memorable ("Home QTH" or "Portable - State Park")
If you operate portable from different grid squares, create separate station locations for each. This matters for VUCC credits.
Step 4: Upload Your First Log
Your logging program exports contacts in ADIF format (.adi or .adif file). Every modern logging program does this.
In TQSL:
- File → Sign and Upload ADIF file
- Select your .adi file
- Choose the correct station location
- TQSL signs each record with your certificate and uploads to the ARRL server
Done. Records typically appear in your LoTW account within minutes, sometimes seconds.
Most logging programs can also upload directly to LoTW without opening TQSL manually. In N1MM+, it's under Config → Configure TQSL. In Log4OM 2, it's in the cloud services settings. Set it up once and forget about it.
Step 5: Check Your Confirmations
Log into your LoTW account at https://lotw.arrl.org/lotwuser/default and click Your QSOs. You'll see:
- QSOs you've uploaded (your side of the log)
- QSO matches (both sides uploaded and agree)
- Award credits available
New users: don't panic if you have zero confirmations immediately. The other station also needs to upload their side. Contest logs often get uploaded in bulk days or weeks after the event. DXpeditions sometimes take months.
Common Mistakes and Fixes
"My certificate request was rejected"
Most common cause: address mismatch with FCC ULS. Log into the FCC ULS (https://wireless2.fcc.gov/UlsApp/UlsSearch/searchLicense.jsp), look up your call, and match your TQSL request exactly to what's on file. Including apartment numbers, abbreviations, everything.
"TQSL says my log has duplicates"
TQSL tracks which QSOs it has already signed and uploaded. If you export your entire log and re-upload, it'll flag the already-uploaded records. This is normal. Just let it skip them or check the box to re-upload all.
"I got confirmations but they don't count for DXCC"
You need to specifically apply confirmations to an award. Go to Your Account → Award Credits → Apply for DXCC or whichever award. There's a small fee per confirmation applied to awards (currently about $0.12 per credit for LoTW users, much cheaper than the paper QSL route).
(I spent my first six months on LoTW assuming confirmations automatically counted. They don't. You have to click the button and pay the nominal fee to apply them toward awards. Nobody told me this until I had 85 DXCC entities confirmed but zero actually credited. Slightly frustrating.)
"The other station says they uploaded but I don't see a match"
Check: same band? same mode? Same date? Times within 30 minutes? Most mismatches come from logging the wrong UTC date around midnight, or from one station logging SSB while the other logged USB (LoTW treats these as the same, but some edge cases with digital modes can cause issues). FT8 contacts must match within a tighter time window.
Integrating With Your Logging Software
Most hams don't manually export and upload anymore. Set up automatic or one-click LoTW upload in your logger:
N1MM+ Logger:
- Config → Configure TQSL
- Point it to your tqsl.exe location
- Set your station location
- After each session: File → Export → Upload to LoTW
Log4OM 2:
- Settings → Cloud Services → LoTW
- Configure TQSL path and certificate
- Can auto-upload after each QSO or batch upload
WSJT-X (FT8/FT4):
- WSJT-X itself doesn't upload to LoTW directly
- Use JTAlert to bridge to a logging program, or export the wsjtx_log.adi periodically and upload through TQSL
Ham Radio Deluxe:
- Logbook → LoTW → Configure → upload. Straightforward once the TQSL path is set.
LoTW vs. Other Confirmation Services
LoTW isn't the only game in town.
QRZ Logbook: Easier to set up but confirmations don't count for ARRL awards. Good for casual tracking.
eQSL: Accepts electronic QSL cards. Some awards accept eQSL confirmations but most major awards (DXCC) don't.
ClubLog: Excellent for DX tracking and OQRS (Online QSL Request System). Not a confirmation service per se, but integrates with LoTW and helps you identify what you need.
Honestly? If you care about awards at all, LoTW is non-negotiable. Use the others alongside it if you want, but LoTW is the backbone.
Tips From Five Years of LoTW Use
A few things I wish someone had told me up front:
- Upload promptly after operating. The other station might check for your upload the next day. If you wait a month, you're the bottleneck in the confirmation chain.
- Keep your certificate backed up in at least two places. Cloud storage and a USB stick. Losing it means starting the postcard process over.
- When you renew your certificate (every three years), TQSL handles it seamlessly if your old cert hasn't expired yet. Don't wait until it expires.
- You can upload old paper logs going back decades. TQSL accepts any QSO date as long as it's within your callsign certificate's valid range. Some hams have uploaded logs from the 1970s.
- The ARRL website sometimes lags. If you upload and nothing shows for 24 hours, check the LoTW system status page before panicking.
Get Started This Weekend
The certificate request and postcard wait is the only real delay. Everything else takes maybe 30 minutes to configure. Request your certificate today, and by next week you'll have a working LoTW setup that takes zero daily effort.
Once it's running, you'll wonder why you put it off. Watching confirmations tick in after a contest weekend is oddly satisfying. Like a scoreboard that fills itself in.
Go set it up.
Reader field notes — share yours
Log in to share your field notes and photos.