Photomaly Achievement Route: All 10 Unlocks and Both Endings

Photomaly’s ten achievements are easier to route as one clean investigation and one deliberate failure than as ten separate chores. Bank the studio actions early, photograph the pixel-faced agent when the opportunity appears, intercept the Day 5 customer, and protect the successful agent quota until Day 6. Only after Family Matters unlocks should you begin the failed-quota run for Reset Protocol.

This is a spoiler route for achievements and the two documented outcomes, not a room-by-room story transcript. It was checked on July 24, 2026 against the launch Steam record, the global achievement list, official Quickfixes #1-#3, and launch-week community observations. Steam identifies Photomaly as AppID 4286120, developed by Revira Interactive, published by Alibi Games, and released on July 21, 2026.

Build the two-run plan around the Day 6 branch#

The achievement descriptions establish ten unlocks. Launch-week guides agree that Family Matters and Reset Protocol represent opposite results of the agent assignment: satisfy the investigation and receive the reward, or fail it and have your memory erased as the game returns to Day 1. They disagree about the minimum work required for the successful quota. Do not gamble the first run on a shortcut.

1. Run one: cooperate. Complete every agent request the current build presents, verify each photographed anomaly, and continue through the Day 6 reward.
2. Run two: fail deliberately. After Family Matters is safely registered, ignore the agent quota and continue until the memory-erasure result awards Reset Protocol and sends the run back to Day 1.

This order protects the time-consuming outcome. A failed quota is simple to reproduce; an incomplete cooperative run can hide one missed camera event until Day 6. Do not delete saves, replace local files, or assume an undocumented manual-save slot is required. The achievement itself describes a return to Day 1, so use that reset as the start of the second route.

Clear the six studio achievements before the quota becomes busy#

Six unlocks come from ordinary work or an early scripted event. Take them as soon as the matching tool appears so that later days contain only the agent, the escaping customer, and the ending branch.

1. Picture Perfect: complete the first customer order correctly. Read the request, take the portrait, prepare the specified print, and hand over the matching envelope. Wait for the order to resolve before changing anything on the computer.
2. Chemical Romance: successfully develop the first film roll. Follow the timer labels shown by the current darkroom station rather than reusing demo-era timings from another source.
3. Customer Service: deliberately hand over an order that does not belong to the customer. Do this after Picture Perfect has registered, so the mistake cannot muddy the proof that your normal workflow works.
4. I’m Something of an Artist: open the Brush/Paint application and make an edit. A community cross-check reports that any actual edit is sufficient; make a visible mark, save or close normally, and wait for the unlock notification.
5. Totally Normal Behavior: set a customer photo as the studio computer’s desktop wallpaper. Use the photo’s current context action rather than merely opening the image.
6. Did I See Someone?: when the power cuts again and the game sends you toward the breaker, approach the panel and let the event play. Two launch guides place the unlock on that interruption rather than on a random free-roam photograph.

If a studio achievement does not appear, confirm the result rather than repeating the entire day. Picture Perfect needs a completed handoff, Chemical Romance needs a successful roll, the wallpaper action must change the desktop, and the art unlock needs an edit rather than simply launching the app. Those distinctions tell you which station to retry.

Take No Face, No Case while the agent is still in front of you#

No Face, No Case asks for a photograph of the agent. When the pixel-faced visitor appears at the counter, do not immediately advance through every line and let him leave. Equip the camera, place the agent clearly in frame, and take the shot. Wait for the achievement before returning to the assignment.

This photo does not replace the agent’s investigative work. It is a separate opportunistic unlock, so treat it like a checkpoint:

• If the photo exists but no achievement appears, check that the agent, not a monitor image of him, was the subject.
• If dialogue has already dismissed him, continue the cooperative route and try again on the next appearance instead of risking the quota with an unnecessary restart.
• If mouse dragging or camera motion behaves erratically, install the current fixes before blaming the framing. Quickfix #1 addressed mixed controller and mouse input; Quickfix #2 addressed random flicks on some wireless mice.

Make every anomaly prove that it registered#

The cooperative run fails when a sighting is treated as enough. Launch observations describe a stronger confirmation: after a valid anomaly photograph, the subject disappears. If it remains in place, reposition and shoot again before the customer cycle advances.

Use this loop whenever the agent’s assignment is active:

1. Accept the current request and inspect anything the agent hands you. Follow the live objective and printer prompt; do not substitute a remembered demo task.
2. Check the security-camera views around a customer arrival or departure. One guide reports that camping permanently at the camera can make the timing harder to read, while new-customer transitions are useful scan points.
3. When a view changes, leave the desk and photograph the physical subject. Frame the full anomaly rather than a corner of it.
4. Confirm that the subject disappears or that the current objective advances. A dramatic image with no state change is a failed report, not progress.
5. Return to the agent workflow and complete the current print or delivery step before starting another ordinary order.

The most detailed launch list available is warning-bannered community evidence, and one of its day headings is internally inconsistent. Use the locations as an audit list, not as a guaranteed schedule:

• Bedroom: an ironing man, a woman beneath the bed, a cat playing with the globe, and a child jumping on the bed.
• Customer room: a creature on the sofa and a hand reaching from the ceiling vent.
• Darkroom and bathroom: a hanging pony, a figure behind the shower curtain, and a cat on the washing machine.
• Backyard: a creature in the trash and a clown near the van.

The same source explicitly separates two human encounters from anomalies: a person in the toilet and a person behind the backyard door. Do not submit them merely because they look unusual. Let the current interaction or objective identify their role. If the build presents a different subject, the security feed and the disappearance/advance signal outrank this launch-week list.

Intercept the Day 5 customer before the distraction works#

Not So Fast is tied to a customer who tries to leave with the completed photo. Launch guides identify him by sunglasses and a red jacket. Photograph him and prepare the requested order normally. The trap begins after the envelope changes hands: he points your attention behind you, then attempts to slip away.

Turn far enough to let the scene advance, then immediately check the counter and exit path. The customer lowers himself and moves away rather than sprinting. Close the distance and interact with him before he clears the room. The useful failure signal is an empty counter with no achievement; if that happens, the interception window was missed, not the photo-processing step.

Keep this attempt separate from a deliberate Customer Service mistake. Not So Fast depends on reaching the theft attempt after the order handoff. Giving this customer random material to save time may prevent the scene from entering the documented state.

Route the Backrooms by feedback, not by a copied turn string#

The Backrooms section matters because a failed escape can disrupt the successful quota run. Sweep the right-hand half first. Launch observers found three ladder pieces there: check a short side room that ends abruptly, the place where the ladder is assembled, and the columns in the second row. That placement comes from a warning-bannered guide, so treat it as a search priority rather than a promise that a later build cannot move an item.

Collecting the first piece activates the mannequin. Keep it in view while moving, and use a camera shot when you need a short safe window. Official Quickfix #3 confirms that the current build increased the mannequin’s stun duration. It also slows the mannequin after you have been caught three times. A catch is therefore recoverable information, but it is still slower than controlling line of sight and moving one piece at a time.

At the final grid, take the photograph the sequence requests and read the developed image. A community guide publishes a fixed series of turns, but the photographed route is the in-game authority and survives localization or route changes better than a copied string. If the photo is unclear, retake it and map one move at a time from the displayed path.

Quickfix #3 also changed the later voice-input sequence. The first attempt is unchanged. If the second attempt detects no voice, a button alternative now appears after five seconds. Wait for that fallback instead of intentionally failing the sequence twice or changing system microphone permissions mid-run.

Lock Family Matters before choosing failure#

Continue the cooperative save to Day 6 only after each agent task has produced a clear state change. The successful route should end with the agent acknowledging the work and delivering the reward associated with Family Matters. Let the scene and achievement notification finish before leaving the game.

If Day 6 produces the memory-erasure outcome instead, audit the previous run with three questions:

• Did every photographed anomaly disappear or advance the objective?
• Did you finish each requested print/delivery step after finding it?
• Did a Day 4 order panel vanish before the task completed? That specific problem was fixed in Quickfix #2.

Do not promote the unverified claim that only one day’s quota is necessary. Two community guides disagree about the minimum, while both agree that cooperation leads to the reward and failure leads to the reset. Completing every presented request is the evidence-safe route.

After Family Matters is visible in Steam, begin the failure run. Ignore the pixel-faced agent’s tasks and continue until Day 6. The agent’s disappointed result, memory erasure, and return to Day 1 are the documented trigger chain for Reset Protocol. At that point the ten-item route is complete: six studio/event actions, the agent photograph, the Day 5 interception, and both sides of the Day 6 branch.

Sources & credits#

• Photomaly on Steam – AppID, developer/publisher, release date, supported features, ten-achievement count, and untouched 1920×1080 JPG screenshots.
• Official Photomaly announcements – launch boundary and Quickfixes #1-#3 for mouse input, Day 4 orders, FPS, Backrooms, and voice input.
• Launch-week community guides were used only for cautious trigger and location cross-checks. Their Steam warning states, a mislabeled day list, and a video-only walkthrough were not hidden or upgraded into official facts.