confirmed
Official trailer
Announcement trailer available
Last checked: 2026-06-10. Last changed: 2026-06-08. Sources: Official BIOHAZARD YouTube trailer.
Source-backed Resident Evil Veronica dossier
Official images are grouped as source material, not used as unsourced decoration.
Last verified: 2026-06-10. Exact release date: not officially confirmed unless a source record says otherwise.
The media page collects official images used across Veronica Hub. Screenshots, store art and trailer posters are labeled with source context so readers can tell whether an image supports a claim, illustrates a page or simply documents official promotional material.
Media can make the site feel less thin, but it should still serve information architecture. Character-related images belong near character notes, setting images support story and original-versus-remake pages, trailer art belongs on the trailer page, and the full archive lives here.
Future media additions should keep descriptive alt text for meaningful images and empty alt text for decorative backdrops. This keeps the site accessible while preserving the dossier style.
confirmed
Announcement trailer available
Last checked: 2026-06-10. Last changed: 2026-06-08. Sources: Official BIOHAZARD YouTube trailer.











1996
Foundational survival-horror grammar established.
1998
Series expands with parallel protagonists and city-level crisis continuity.
1999
Recurring threat pressure model becomes central.
2000
Narrative bridge for the Veronica storyline enters.
2002
Prequel branch adds companion-first puzzle rhythm.
2005
Major modernization pivot: cinematic action and movement tuning.
2009
Co-op and action scale increase across mission architecture.
2012
Campaign structure becomes multi-protagonist and broad.
2017
First-person horror reset.
2019
High-confidence legacy rebuild of a classic chapter.
2020
Urgency-focused remasterized conversion of RE3.
2021
Current era broad action-horror and boss sequencing established.
2023
Full legacy conversion at RE Engine standards.
2027
Capcom confirms platform set and release window.
RE1
Story context: Established fixed-camera survival mechanics, item friction and room-based tension before the series shifted to modern controls.
Why include: This is the oldest playable anchor. It defines what players still expect from survival horror rhythm in later remakes.
Origin: RE1 defined the franchise’s core architecture and became the oldest benchmark before every later gameplay conversion.
RE2
Story context: Extends the franchise with Claire and Leon in parallel arcs, and a wider crisis after the Raccoon City incident.
Why include: Most useful legacy baseline for inventory rhythm and campaign urgency before modern remakes.
Origin: RE2 preserved the original survival loop while scaling scope, making it a direct historical comparator for modern tuning.
RE3
Story context: Introduces a recurring threat pressure model centered around the Nemesis chase and escape rhythm.
Why include: Important to understand how threat persistence changed pacing before modern action-remake design.
Origin: RE3 formalized repetitive pursuit pressure, which later games and remakes later borrow for intensity calibration.
RE CV
Story context: Direct narrative predecessor for Veronica, extending the Claire/Chris arc through broader island and travel settings.
Why include: The most relevant non-remake anchor because Veronica inherits setting and character context from this node.
Origin: Code Veronica is the direct predecessor chain, so relation mapping for Veronica starts here before any modernization.
RE0
Story context: Prequel branch with Rebecca and Billy, using a companion-first puzzle and combat structure before Veronica’s broader arc.
Why include: Useful if visitors want the predecessor style before full cinematic action transitions.
Origin: RE0 preserves early design rhythm with partner framing and helps explain how the series handled tension before later remasters.
RE4
Story context: Moves the series into more cinematic action-survival using Leon in a wider mission geography.
Why include: This is the structural pivot before RE4 Remake shows the full modernization path.
Origin: RE4 introduced the major shift toward modern action timing, a key reason RE4 Remake is in the playable comparison queue.
RE5
Story context: Expands the story into broader action and cooperative structures with stronger mission throughput.
Why include: Important contrast for visitors asking why some Veronica claims feel more restrained than action-era entries.
Origin: RE5 illustrates a short period where action tempo outpaced narrow survival structure; valuable for direction clarity.
RE6
Story context: Splits into multiple protagonists and campaign branches, increasing structural complexity.
Why include: A cautionary comparison for scope and pacing: useful when discussing what Veronica likely did not inherit.
Origin: RE6 showed how broad campaign design can dilute intensity; it helps position why remakes moved back toward tighter control.
RE7
Story context: Re-centers the series around first-person dread and tighter house-scale immersion.
Why include: Critical modern baseline before RE8 and before current remake expectations in narrative tone.
Origin: RE7 introduced the perspective reset that made later releases feel more intimate and immediate in threat reaction.
RE2 Remake
Story context: Modern RE2 rebuild with near-complete system refresh on a proven chapter skeleton.
Why include: Most reliable modern anchor for how a legacy chapter is remade for current audience habits.
Origin: RE2 Remake is the current proof point for Capcom’s baseline conversion approach, directly useful for Veronica expectation framing.
RE3 Remake
Story context: Rebuild of RE3 with compressed pacing and modern threat readability.
Why include: Supports players comparing campaign density and urgency before deciding on Veronica expectations.
Origin: RE3 Remake demonstrates what a short remaster-like conversion can preserve while changing input and timing conventions.
RE8
Story context: Post-RE7 continuation with stronger boss-driven progression and broader modern traversal.
Why include: Current mainstream reference for players comparing how modern scale and pacing may continue into Veronica.
Origin: RE8 marks the recent benchmark before Veronica and helps place expectations for atmosphere versus combat density.
RE4 Remake
Story context: Current modernized form of RE4 with full contemporary control and encounter systems.
Why include: Most direct modern template for expected gameplay translation quality and tone transfer.
Origin: RE4 Remake is the nearest official modern reference for how Capcom remasters legacy structure at 2023-level polish.
PlayStation, PC, Dreamcast
Classic baseline with deliberate movement and strict inventory management, useful for understanding original survival pressure.
Node: RE1
Story context: Established fixed-camera survival mechanics, item friction and room-based tension before the series shifted to modern controls.
Origin: RE1 defined the franchise’s core architecture and became the oldest benchmark before every later gameplay conversion.
Why include: This is the oldest playable anchor. It defines what players still expect from survival horror rhythm in later remakes.
Year: 1996
PlayStation, PC, Xbox
Sharper room pressure and clearer combat-readability than RE1, with stronger checkpoint cadence.
Node: RE2
Story context: Extends the franchise with Claire and Leon in parallel arcs, and a wider crisis after the Raccoon City incident.
Origin: RE2 preserved the original survival loop while scaling scope, making it a direct historical comparator for modern tuning.
Why include: Most useful legacy baseline for inventory rhythm and campaign urgency before modern remakes.
Year: 1998
PlayStation, PC, Dreamcast, Xbox
Higher urgency profile with timed pressure from repeating boss pressure and tighter encounter resets.
Node: RE3
Story context: Introduces a recurring threat pressure model centered around the Nemesis chase and escape rhythm.
Origin: RE3 formalized repetitive pursuit pressure, which later games and remakes later borrow for intensity calibration.
Why include: Important to understand how threat persistence changed pacing before modern action-remake design.
Year: 1999
Dreamcast, PlayStation 2, PC
Longer transitions and sustained movement segments, while still grounded in classic survival rhythm.
Node: RE CV
Story context: Direct narrative predecessor for Veronica, extending the Claire/Chris arc through broader island and travel settings.
Origin: Code Veronica is the direct predecessor chain, so relation mapping for Veronica starts here before any modernization.
Why include: The most relevant non-remake anchor because Veronica inherits setting and character context from this node.
Year: 2000
GameCube, PS3, PS4, PC
Twin-role pacing and checkpoint placement emphasize sequencing and short-term strategy.
Node: RE0
Story context: Prequel branch with Rebecca and Billy, using a companion-first puzzle and combat structure before Veronica’s broader arc.
Origin: RE0 preserves early design rhythm with partner framing and helps explain how the series handled tension before later remasters.
Why include: Useful if visitors want the predecessor style before full cinematic action transitions.
Year: 2002
GameCube, PS2, PC, Xbox
Stronger movement and enemy density profile than earlier entries while keeping survival constraints in place.
Node: RE4
Story context: Moves the series into more cinematic action-survival using Leon in a wider mission geography.
Origin: RE4 introduced the major shift toward modern action timing, a key reason RE4 Remake is in the playable comparison queue.
Why include: This is the structural pivot before RE4 Remake shows the full modernization path.
Year: 2005
PS3, Xbox 360, PS4, Xbox One, PC
Larger combat spaces and faster flow, useful for understanding modern action-pressure branches.
Node: RE5
Story context: Expands the story into broader action and cooperative structures with stronger mission throughput.
Origin: RE5 illustrates a short period where action tempo outpaced narrow survival structure; valuable for direction clarity.
Why include: Important contrast for visitors asking why some Veronica claims feel more restrained than action-era entries.
Year: 2009
PS3, Xbox 360, PS4, Xbox One, PC
High throughput with heavier sequence density and mission segmentation.
Node: RE6
Story context: Splits into multiple protagonists and campaign branches, increasing structural complexity.
Origin: RE6 showed how broad campaign design can dilute intensity; it helps position why remakes moved back toward tighter control.
Why include: A cautionary comparison for scope and pacing: useful when discussing what Veronica likely did not inherit.
Year: 2012
PC, PS4/PS5, Xbox One/Xbox Series X|S
Close-quarters exploration and fear rhythm become stronger than classical static-room sequencing.
Node: RE7
Story context: Re-centers the series around first-person dread and tighter house-scale immersion.
Origin: RE7 introduced the perspective reset that made later releases feel more intimate and immediate in threat reaction.
Why include: Critical modern baseline before RE8 and before current remake expectations in narrative tone.
Year: 2017
PC, PS4/PS5, Xbox One/Xbox Series X|S
Clearer input responsiveness, improved movement pacing and preserved inventory pressure under modern control systems.
Node: RE2 Remake
Story context: Modern RE2 rebuild with near-complete system refresh on a proven chapter skeleton.
Origin: RE2 Remake is the current proof point for Capcom’s baseline conversion approach, directly useful for Veronica expectation framing.
Why include: Most reliable modern anchor for how a legacy chapter is remade for current audience habits.
Year: 2019
PC, PS4/PS5, Xbox One/Xbox Series X|S
Faster loop compression and clearer enemy telegraphing for modern players without full structural rewrite.
Node: RE3 Remake
Story context: Rebuild of RE3 with compressed pacing and modern threat readability.
Origin: RE3 Remake demonstrates what a short remaster-like conversion can preserve while changing input and timing conventions.
Why include: Supports players comparing campaign density and urgency before deciding on Veronica expectations.
Year: 2020
PC, PS4/PS5, Xbox One/Xbox Series X|S
Large modern action-horror map language with tactical movement and boss rhythm.
Node: RE8
Story context: Post-RE7 continuation with stronger boss-driven progression and broader modern traversal.
Origin: RE8 marks the recent benchmark before Veronica and helps place expectations for atmosphere versus combat density.
Why include: Current mainstream reference for players comparing how modern scale and pacing may continue into Veronica.
Year: 2021
PC, PS4/PS5, Xbox One/Xbox Series X|S
Tighter combat windows, revised pacing and stronger player agency under legacy camera legacy converted to modern expectations.
Node: RE4 Remake
Story context: Current modernized form of RE4 with full contemporary control and encounter systems.
Origin: RE4 Remake is the nearest official modern reference for how Capcom remasters legacy structure at 2023-level polish.
Why include: Most direct modern template for expected gameplay translation quality and tone transfer.
Year: 2023
Markiplier / PC Gaming
Game-first creators with long-format impressions.
Reason: Good for audience who wants a raw first-play reaction before comparing Veronica.
AngryJoeShow
High-visibility game creator with long-form review style.
Reason: Useful for players checking if the remake tone is “fun + scary” rather than “pure puzzle-only”.
GameSpot
Editorial channel with hands-on and trailerview content.
Reason: Useful for fast scene checks when visitors want official clip-heavy coverage.
IGN
Long-form game coverage from launch and trailer release periods.
Reason: Helps users balance fan edits with mainstream breakdowns.
The Game Theorists
Narrative/gameplay design explanations.
Reason: Useful for players who want to understand combat and level logic direction.
TheRadBrad
Walkthrough-focused creator with full-playstyle pacing coverage.
Reason: Useful for players who compare campaign flow and mission structure before making a final opinion.
jacksepticeye
High-energy reaction creator with practical setup and progression takes.
Reason: Adds a broad creator perspective before readers dive into claim-heavy source sections.
VGC Channel
Cross-region RE-focused gameplay captures.
Reason: Good for players who prefer practical gameplay snippets over review essays.
GameXplain
Cross-platform video and trailer coverage with practical gameplay snippets.
Reason: Good for broad platform comparison and clip discovery.
Independent fan-made information hub. Veronica Hub is not affiliated with or endorsed by Capcom.
Veronica Hub does not host ROMs, ISOs, cracks, emulators or unofficial downloads.
Veronica Hub marks claims as confirmed, reported or unknown. Unknown details stay unknown until a cited official source changes them.