Skip to content
View in the app

A better way to browse. Learn more.

LCPDFR.com

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Leaderboard

Popular Content

Showing content with the highest reputation since 06/23/2010 in Guidelines

  1. Site Wide Guidelines

    TheLegendary and 21 others reacted to Sam for a guideline

    22 points
    Site Wide Guidelines Don't be abusive or discriminatory No trolling Don't post porn, nudity (partial, full, or censored), or be overly profane Only post things that contribute to the discussion at hand Do not involve money in requests - we cannot guarantee the validity of transactions and our site is not for you or others to make money from, outside of the donation function. Asking for reputation is not allowed Refrain from posting short replies such as "lol", "+1", "cool", etc. Keep the site tidy - use spoilers for logs, attach images only when needed, don't deviate from the standard font unless necessary Don't bump your threads or reply to threads older than 30 days (unless they're pinned) Do not add images to posts unless those images positively contribute to the discussion at hand No advertising of external communities or discussions/rants/drama regarding them (advertising is only permissible on your profile and signature) Don't post or share stolen mods Report all potentially infringing content - do not attempt to address it publicly Don't make or use multiple accounts Do not conduct any form of piracy (uploading original game files, sharing cracks and so on). Do not obstruct moderator investigations or otherwise interfere with the operation of the site. This includes telling other members what to do. Impersonation of any staff member is prohibited All content is subject to moderation when necessary. Content can potentially be removed at any time for any reason. Do not send members PMs asking for support. We have the forums for a reason. If you have reported something and noticed that nothing has been done about it, think about what you are reporting. It may not have been in violation of the Guidelines. Feel free to message a moderator and inquire about the report. Do not file another report. These guidelines are an easy to read abbreviation of our full Terms. They are not a substitute.
  2. File Guidelines

    snailvirus and 20 others reacted to Sam for a guideline

    21 points
    File Guidelines Every part and contribution must be properly credited, and may only be used with permission granted by the author before upload. For car mods, this includes: Origin of original vehicle: Original game, and those who helped convert it. Texture creator(s). Credits for every single part (rims, computer, centre console, lightbars, lights, spotlights, antennas, etc). Descriptions must only advertise features and content present in the uploaded file. Authors using AI tools to support development or the creation of modifications must verify that all advertised features actually exist within the mod. Credits should be entirely complete. "Unknown" authors are not permitted. Credits should be posted in the "Credits" area of the upload page. If you have a text file with full credits, these should be copied to that area. "Credits included" or similar text is not sufficient. File updates must be published as updates, not brand new submissions. At least one in-game or OpenIV screenshot is required. For texture, car or ped packs, every vehicle, skin or ped must be shown in the screenshots. However, if there's one valid screenshot plus a detailed video in the description showing every component, that's generally okay. The main screenshot on any file should always depict the mod itself. Real-world images, while not prohibited if in game shots accompany them, should not be the main image. Do not upload packs containing mods not created or edited by yourself. Do not upload improper file types in the wrong categories (no weapons in vehicle models, etc.). If uploading a pack of files you made yourself, create separate submissions for each type (vehicles, weapons, etc.). When uploading texture submissions, do not include the model that they are made for (only a link instead), and include only the raw texture (in png, bmp, jpg, etc. format). Do not upload wtd or ytd files. Do not upload executable files, unless absolutely necessary. For example, you should never use a self-extracting .exe archive, or an installer, for Vehicle Models and Vehicle Textures. OIV files are okay. We typically do not permit launchers or standalone executables unless the security risk is clearly justified. Before uploading any such files, please obtain approval from management. Note that the criteria for approval are strict. Do not upload on behalf of another person -- work you upload must be contributed to in some way by yourself. If you used AI as part of your modification, you must disclosure it using the AI disclosure options. There are separate options for description, images and mod content. More information can be found here. Reviews must contain a valid review text (No "1 star" comments and so fourth). Reviews may only be made after you have downloaded and used the file. File reviews should relate directly to the item at hand. Comments written as reviews, and off topic posts, will be removed from the Reviews section of files. Do not just upload text files with a link to the file elsewhere, without prior agreement from LCPDFR.com Management. Files must be uploaded to LCPDFR.com, and cannot be simply text file links to off-site content. Contact @Cyan if your file exceeds the maximum file size, or you're having issues uploading your file. We can now increase the limit to 4GB on a per-account basis if this is needed. The following are forbidden from being uploaded to or shared on our network: Files and tools which we deem to be malicious in nature, such as spyware, adware, viruses and other inappropriate content. Game modifications or other files which interfere with or otherwise adversely affect the game or the playing experience for yourself or others. Any other content which we deem poses a threat or risk to our services, members or communities. A reminder: Our advertising guidelines We've clarified our policy on advertising on files. You can see this on the Wiki page here. Please also note that file comments are not exempt from our advertising rules either. This does not mean that you cannot ask people to reach out to you directly or through Discord for specific or complex problems, but if the answer is as long as your Discord link, you might as well post it directly. File Listings On occasion, files may be delisted if we do not think they are intended for a general audience. This can include, for example: In-jokes only relevant to a small population (e.g. a Discord server specific joke, fringe political jokes, a joke intended for another member). Files which have excessive implied profanity or implied sexual content which does not otherwise violate the Community Guidelines. April fool's content in good jest, e.g. submissions which are something else than their description applies but with no malicious intent. (we may for example delist the file post April 1st) Description/screenshots which are on the border of NSFW, for example, particularly revealing anime which is not hentai but suggestive. Delisted files will continue to be hosted and available via their direct link, but will not appear on the site via recommends, in categories, in search or in activity feeds. A file being delisted does not penalise the submitter in any way.
  3. File Reporting Guidelines

    Faya and 3 others reacted to Will for a guideline

    4 points
    The following list details what we expect from reports in relation to files. If you fail to follow these general guidelines, there may be a delay in processing your report, or it may be closed without taking any action. Generally, you will not be punished for not following these guidelines, however repeated misuse of the reporting system may result in infractions. Always include a message with your report - do not leave the message area blank. Leaving the message area blank on a file report will result in the report being closed immediately. If you are reporting a file for having incomplete or incorrect credits, include the correct credits in your report. If you believe a file has been directly reuploaded by someone other than the original author, include a link to the original file. If you believe a file is using parts that the uploader does not have permission to use, you should contact the author of the parts instead. We will not process reports regarding permission issues unless the original author submits the report. If you are the original author reporting a stolen file/part, always include evidence. The burden of proof always falls on the reporter, not the uploader. Evidence should be included in the report itself to speed up processing instead of saying "PM me for proof." Do not publicly accuse anyone of mod theft. This is against our site rules and only delays the processing of your report. You may check the progress of your report in our Support Dashboard. See this topic for more information.
  4. Website API guidelines

    Michael21107 and one other reacted to Cyan for a guideline

    2 points
    The specific rules of the API differ depending on key type. General Guidelines We ask that you use one key per application. Alternating between API keys in the same application to bypass limits may cause your access to the API to be revoked. Please always send a User-Agent header that uniquely identifies your bot or application. LCPDFR.com data should only be used for non-commercial uses. We reserve the right to not issue, or approve requests for the API for any reason. We may contact you to ask about your use case before issuing keys. We reserve the right to revoke API keys for any reason, or no reason at all. We would in general contact you about usage of the API before this would be a problem. Downloads: Version Checking Key This key type is designed for developers of callouts and plugins to check for updates to their own plugins and callouts. This type of API key can only access our version endpoint, and use is uncapped. Downloads: Public API Key This key type can be used for any other non-commercial purposes, including: version checker applications, Discord bots, your own websites. Usage is provisionally capped at 1,800 calls an hour.
  5. Gallery Guidelines

    gapcomputer reacted to Sam for a guideline

    1 point
    Gallery Guidelines Don't use the GTA IV or GTA V Categories to upload images not taken directly from GTA IV or GTA V, respectively. Images may not be edited in a way that detracts from the in-game content, but edits that enhance the in-game content is fine. For example, editing in a news overlay is fine, but editing in Darth Vader fighting on an in-game CVPI is not. Renders/ZMod screenshots may not be posted in our gallery (use forum threads instead for showcasing WIP projects). Don't use the Gallery to advertise your YouTube accounts or websites. Don't use the Gallery to direct users to download modifications from other websites. Real world images are strictly prohibited. Showing off models you have no intention of ever releasing on LCPDFR.com is prohibited. Images may be removed if they are uploaded repeatedly or if they otherwise spam/clutter the site. Images may not spam the gallery. The random gallery can be used for any game except GTA IV / GTA V.
This leaderboard is set to London/GMT+01:00

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.