Left 4 Dead 2 Screenshots and Images - PC

Left 4 Dead 2
  • Publisher: Electronic Arts
  • Genre:Action
  • Developer: Valve
  • Release Date:Nov 17, 2009
  • # of Players:1 player
  • ESRB:M - Mature (Blood and Gore, Intense Violence, Language)
  • Platforms:
Game Description:In the follow-up to Valve's wildly popular zombie-slaying FPS, players assume the roles of four new characters, as they struggle to survive against unending hordes of the undead beneath the sunny skies of the American South. Dispose of the newly designed zombie types with the help of new melee weapons, including an ax, a chainsaw, a baseball bat, and even a frying pan. And thanks to the addition of even more modes, maps and items, players can expect to have their hands full when the zombie apocalypse rears its undead head once again.
G4TV Rating
4 / 5
  • Avg User Rating
    (24 Ratings)
    4.8 / 5
  • Rate This Game
  • X-Play Recommends - Left 4 Dead 2: Cold Stream

    Posted: August 20, 2012

    1,951 Views | 01:53

  • X-List: Best 4-Player Co-Op Games

    Posted: March 6, 2012

    20,743 Views | 01:24

  • Mod This: Left 4 Dead

    Posted: August 2, 2011

    15,742 Views | 02:30

  • Best of 2010: Best DLC

    Posted: December 14, 2010

    18,140 Views | 00:54

  • X-Play Recommends Left 4 Dead DLC The Sacrifice

    Posted: October 21, 2010

    22,894 Views | 01:55


Runtime Error

Server Error in '/' Application.

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

<!-- Web.Config Configuration File -->

        <customErrors mode="Off"/>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

<!-- Web.Config Configuration File -->

        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>