Hidden message ideas for geocaching (and ARGs)

Most geocaching puzzles hide exactly one thing: the coordinates. You solve a cipher, the numbers fall out, you drive to the spot. It is a good game and I have lost real weekends to it. But there is a quiet limit built into the format. Once anyone cracks the puzzle, they get everything, the cache, the log, whatever you tucked inside. There is no such thing as a clue that opens for one specific person, because the whole hobby runs on a shared, public logbook.

That gap is what this post is about. If you build puzzles out in the world, geocaches, an ARG, a chain of clues across a city, you sometimes want the opposite of a public solution. You want a payload that resolves for the finder who earned it and stays shut for everyone who just wandered past.

The classic hides, and where they stop

The traditional toolkit is deep, and you should use it. It is what makes the hunt feel like a hunt:

• Substitution ciphers like pigpen (the Masonic grid) and Caesar shifts, which read as gibberish until someone spots the pattern.
• The Baconian cipher, where a message hides in the styling of ordinary text, plain letters as one value and italics as another.
• Morse tapped into the length of dashes, a rhythm painted on a fence, or the spacing of objects.
• ASCII stereograms, where a wall of monospace text pops into a word once your eyes relax.

These are wonderful, and they are all the same kind of thing: obfuscation. The message is right there in the open, scrambled by a rule. Anyone who knows or guesses the rule reverses it. That is a feature for the journey and a problem for the destination. If your final reward is a Baconian ciphertext, the first sharp finder posts the plaintext in the log and the puzzle is over for the next hundred people.

Leave a payload, not just a pointer

The shift in thinking is small but it changes what you can build. Instead of hiding the coordinates and leaving a plain reward at the end, hide the reward itself and make it open only for the right person.

Two carriers work well in the field. A QR code you print and stash: to a random scanner it looks like a normal link to a normal page, but the real message rides underneath for someone who has the key. Or an ordinary photo you send or leave on a phone at a station: to anyone else it is just a picture. The finder opens either one in GhostCode with the key you gave them, and the hidden part appears.

Be honest with yourself about what that requires, because it shapes the design. The finder needs the app, and they need the key, and you share that key separately from the QR or the photo. So this is not a drop-anywhere trick for a stranger. It is a mechanic for a game where you already control an earlier step, which, if you are running a puzzle, you do.

Where the key comes from is the whole trick

The key is the thing the finder earns. That single idea is what turns a linear puzzle into a gated one. A few ways to hand it over without handing it to everyone:

• Make the answer to an earlier stage the key to a later one. Solve the pigpen at station three, and the decoded word is the key for the QR at station five.
• Use a shared memory as the key for a personal hunt, a date, a place, an inside joke only your person would type.
• Hide the key in the physical world and the payload in the digital one. A word carved into a bench opens a photo you texted them that morning.

This is exactly how the best ARGs already feel. Creators chain clues across physical and online spaces, a QR on a billboard here, a code buried in a spectrogram there, so that solving requires gathering pieces from more than one place. Adding a real gate means a leaked answer to one stage does not spill the whole rabbit hole. The person who skipped the work hits a page that looks finished and never sees there was more.

Building a chain that actually holds

Here is a shape I like for a wild puzzle with three or four legs. The first legs are pure classic craft: ciphers, coordinates, a physical container, all public, all solvable by anyone who shows up and thinks. Let that part be generous. Then the final leg is the gated one. The last container holds a printed QR. Scan it cold and you get a tidy little page that reads like the end of the trail. But the finder who solved leg three is carrying a word, and that word is the key that opens the actual finale hidden under the same code.

For a geocaching context specifically, this fits neatly as a side quest or a bonus attached to a mystery cache, rather than the logged coordinates themselves. The public part stays public, which keeps it a real cache. The gated part is the extra layer for the finder who wanted more than a signature in a logbook. If you have run a QR code scavenger hunt before, this is the same skeleton with one leg that refuses to open for the crowd.

Be straight about the limits

A gate is not a vault, and pretending otherwise ruins the trust that makes people play your games. Two honest caveats. First, once your finder opens the message, it is on their screen, and a screenshot taken in that moment is out of everyone's hands, including yours. If the payload is a surprise, that is fine, they are the intended audience. Second, the whole mechanic depends on both sides using the app: you to hide it, them to open it. To a scanner without the app and the key, a GhostCode QR is just a QR and a GhostCode photo is just a photo, which is the point, but it also means this is a tool for a game you are running, not a way to smuggle something past a determined stranger. Say that up front to your players and the reveal lands better.

Questions people ask

Can you hide a message in a geocache without leaving paper?

Yes. Instead of a physical note, the final container can hold a printed QR code or point to a photo you sent ahead. The readable message is not sitting in the open for the next finder to copy out of the log, because it only resolves for the person who has the key.

How do you make a cache only one person can solve?

You cannot gate the coordinates themselves, and you should not try, since a listed cache is meant to be findable. What you can gate is a bonus payload attached to it. Hand the key to your intended finder through an earlier stage or a shared memory, and the extra content opens for them and stays closed to the casual finder who just signs the log.

Do finders need a special app?

For the gated leg, yes, they open it in GhostCode with the key. That is the trade for a clue that does not spill the moment it is solved. Keep the earlier legs of your hunt as plain classic puzzling so nobody needs anything but a pencil and a good eye to play along.

Is this against the spirit of a public logbook?

Not if you keep the logged cache public and treat the hidden payload as a side layer. The signature log stays a signature log. The gated reveal is a bonus for the finder who chased the extra thread, closer to a personal scavenger hunt finale than to a locked cache.