What is That's Not My Neighbor Online
That's Not My Neighbor Online is the browser-based version of the horror-themed identity verification game that became popular around 2024. You play as a doorman at a hotel or apartment building, and your job is to check the IDs and documents presented by visitors to determine whether they are who they claim to be or an imposter. The twist is that imposters look nearly identical to real residents, but their documents contain subtle inconsistencies — wrong dates, mismatched photos, altered stamps. The online version runs directly in a web browser without needing to download anything, which is why people search for it specifically. I've spent more hours than I'd like to admit on this game, and honestly, the browser version has some quirks that the standalone release doesn't. The most frustrating one is that the document details sometimes render slightly differently depending on your browser. I noticed this when playing on Firefox versus Chrome — certain text elements on the ID cards would shift or blur at different zoom levels, making legitimate discrepancies harder to spot. The workaround was simple: switch to Chrome, set zoom to 100%, and keep a second monitor or window open to reference known-correct document layouts from community wikis.
How to Play That's Not My Neighbor Online
The core loop is straightforward. Each round, a new visitor arrives at your desk. They hand you an ID card, a residency document, or sometimes a warrant or authorization form. You need to cross-reference everything against a reference sheet provided at the start of the shift. If something doesn't match — a birth date that contradicts the photo age, a stamp from the wrong municipal office, a signature that doesn't align with the name — you reject the person. If you accept an imposter, the game tracks how many mistakes you've made. Three rejections in a row and it's game over. Here's what most guides don't mention: the reference sheet itself can be misleading. Some of the "official" document templates include minor inconsistencies built into them — faded text, partial stamps, intentionally ambiguous addresses. I wasted an entire shift once because I was flagging a residency document as fraudulent when it was actually correct; the reference sheet had a typo in the address format that made it look like the visitor's document was wrong. The lesson is to check for the same error category appearing across multiple documents before rejecting someone. If two different cards share an oddity, it's likely a system issue, not a forgery.
Another thing beginners consistently get wrong is the time pressure element. The game runs on a hidden timer, and while it doesn't show you a countdown, each decision consumes real seconds. If you spend too long examining one document, the game starts rushing the next visitor in, which means you'll make hasty errors on the following checks. I found that setting a personal limit of about 30 seconds per visitor keeps you in the zone. Anything longer and the game's pacing works against you.
Advanced Document Inspection Techniques
The game has multiple document types, and each one requires a different inspection approach. ID cards are the most common, but you'll also see residency permits, work authorizations, visitor passes, and occasionally medical certificates. The game pulls from a known set of error categories, and understanding these is more useful than trying to memorize every possible document. Photo-to-document mismatch is the easiest error to spot but also the one most players miss first. The photo on the ID might show a person with glasses when the reference photo clearly doesn't, or the hair color differs between the card and the visitor standing in front of you. Pay attention to ear shape and eye color specifically — those are the details most commonly altered in the game's forgery engine.
Date inconsistencies are the second most common error type. A resident card might have an issue date that's after the expiration date, or a birth year that doesn't align with the apparent age in the photograph. I've seen players overlook this because they're focused on the photo comparison and stop checking the numerical data. Flip the habit: check the numbers first, then the photo. Numbers are easier to verify quickly and catch glaring contradictions. Stamp and seal analysis is where the game gets tricky. Some documents use fake municipal stamps that look plausible at a glance but have incorrect jurisdiction codes or wrong years printed inside the seal border. There's a specific stamp type — the "Prefeitura Municipal" circular seal — that appears frequently, and the forgery almost always has the year positioned incorrectly inside the ring. I learned this through repeated failures early on. Now I scan for that seal first on any document that includes one.
👉 Clique no botão abaixo para saber mais sobre o assunto!
Common Mistakes and How to Avoid Them
The biggest mistake I see people make is treating the game like a memory test. It isn't. It's a pattern recognition exercise under mild stress. Trying to memorize every possible document variant is impossible because the game generates combinations procedurally. Instead, build a mental checklist you run through every single time, regardless of document type: One: verify the name matches across all fields. Two: check the photo against the physical description. Three: cross-reference dates for logical consistency. Four: inspect stamps and seals for jurisdiction accuracy. Five: look for any field that was filled in a different font or ink color than the rest — that's often the telltale sign of a forgery edit.
I used to skip step five consistently. I'd catch four out of five errors and reject the document, but I'd occasionally reject a perfectly valid one because I was being too aggressive on the ink mismatch criterion. The fix was to treat ink/font variation as a "maybe" flag, not a "reject" flag. Only reject on that basis if at least one other discrepancy also exists. This small adjustment improved my accuracy from roughly 60% to about 82% over a week of daily play.
The Browser Version's Hidden Issues
Running That's Not My Neighbor Online through a browser introduces problems that the native app doesn't have. The audio cues — specifically the tension music that intensifies as you approach a mistake threshold — are inconsistent across browsers. Firefox tends to lag the audio by half a second compared to Chrome, which means you might not hear the warning signal before making an error. If you rely on audio feedback (and I recommend you do), Chrome is the only reliable option. There's also a known issue with the game's fullscreen mode on mobile devices. The document detail becomes too small to read on screens under 6 inches. I discovered this when a friend tried playing on a phone and couldn't distinguish between a legitimate document and a forged one because the text was pixelated. The solution is to play on a tablet or laptop, or simply keep the browser window maximized at its default size rather than using fullscreen.
One more edge case: if you refresh the page mid-shift, your progress resets completely. There is no save feature in the browser version. I lost a 47-visitor run once because my internet flickered for two seconds and the page reloaded. That's a hard limitation of the web build. The standalone versions sometimes offer manual save states, but the online iteration does not. Plan your sessions accordingly — treat each browser tab as a single continuous attempt.
Is There a Download Alternative Worth Considering
If the browser limitations bother you, the game is also available on Steam and various mobile platforms as a paid download. The core gameplay is identical, but the native versions handle document rendering more consistently, include an autosave feature, and support higher resolution textures that make forgery detection significantly easier. I prefer the desktop version for serious play. The browser version is fine for casual sessions, but if you're trying to chase high scores or complete difficulty variants, the downloadable version removes enough friction to matter. The browser version remains free and accessible, which is why most people find it first. Just be aware that you're working with a slightly inferior experience, and a few of the techniques I described above — particularly the chrome-specific recommendations — exist because of those compromises. Play smart, keep your checklist consistent, and don't trust the reference sheet blindly.
