Unreal Engine Uproject

Unreal Engine project configuration file

.uproject

Validate

Check your file against this schema

Opens the validator with this schema already loaded. Paste your .uproject and it validates in your browser — nothing is uploaded.

Validate a .uproject → View raw schema

Reference

Fields

Generated directly from the schema, following local $refs, to two levels of nesting.

Field	Type	Description
`AdditionalPluginDirectories`	`array<string>`	List of additional directoreis to scan for plugins default: `[]`
`DisableEnginePluginsByDefault`	`boolean`	Indicates that enabled by default engine plugins should not be enabled unless explicitly enabled by the project or target files. default: `false`
`IsEnterpriseProject`	`boolean`	Indicates if this project is an Enterprise project. default: `false`
`Category`	`string`	Category to show under the project browser.
`Description`	`string`	Description to show in the project browser.
`EngineAssociation`required	`string`	The engine to open this project with. Either <major>.<minor> version (4.27, 5.4, etc), unique Engine identifier, blank for directory-based discovery, or relative path.
`EpicSampleNameHash`	`number`	A hash that is used to determine if the project was forked from a sample.
`FileVersion`required	`number`	Descriptor version number. default: `3`
`Modules`	`array`	List of all modules associated with this project.
`Plugins`	`array`	List of plugins for this project (may be enabled/disabled).
`PostBuildSteps`	`object`	Custom steps to execute after building targets in this project.
`PreBuildSteps`	`object`	Custom steps to execute before building targets in this project.
`TargetPlatforms`	`array<string>`	Array of platforms that this project is targeting.

Audit

What we found in this schema

Declared draft: draft-07
Validates cleanly against its own meta-schema.
Uses non-standard keywords that generic validators ignore: annotations.
38 properties, 100% carrying a description, max nesting depth 6.

Standards

Specification sections for the keywords in this schema

Keyword	Document	Section
`$comment`	JSON Schema Core, draft 2020-12	§8.3 — Comments With "$comment"
`$id`	JSON Schema Core, draft 2020-12	§8.2.1 — The "$id" Keyword
`$ref`	JSON Schema Core, draft 2020-12	§8.2.3.1 — Direct References with "$ref"
`$schema`	JSON Schema Core, draft 2020-12	§8.1.1 — "$schema"
`additionalProperties`	JSON Schema Core, draft 2020-12	§10.3.2.3 — "additionalProperties"
`default`	JSON Schema Validation, draft 2020-12	§9.2 — "default"
`description`	JSON Schema Validation, draft 2020-12	§9.1 — "title" and "description"
`enum`	JSON Schema Validation, draft 2020-12	§6.1.2 — "enum"
`items`	JSON Schema Core, draft 2020-12	§10.3.1.2 — "items"
`properties`	JSON Schema Core, draft 2020-12	§10.3.2.1 — "properties"
`required`	JSON Schema Validation, draft 2020-12	§6.5.3 — "required"
`type`	JSON Schema Validation, draft 2020-12	§6.1.1 — "type"
`uniqueItems`	JSON Schema Validation, draft 2020-12	§6.4.3 — "uniqueItems"

Documents

JSON Schema Core, draft 2020-12 — JSON Schema: A Media Type for Describing JSON Documents, A. Wright, H. Andrews, B. Hutton, G. Dennis, Eds., 2022. draft-bhutton-json-schema-01. An expired Internet-Draft with no formal standing in the IETF standards process; it is nonetheless the specification of record for JSON Schema 2020-12, published by json-schema.org.
JSON Schema Validation, draft 2020-12 — JSON Schema Validation: A Vocabulary for Structural Validation of JSON, A. Wright, H. Andrews, B. Hutton, Eds., 2022.
RFC 8259 (STD 90) — The JavaScript Object Notation (JSON) Data Interchange Format, T. Bray, Ed., 2017. The format a schema describes.
RFC 6901 — JavaScript Object Notation (JSON) Pointer. Defines the pointer syntax used by $ref fragments and the ~0 / ~1 escapes.

Source

Attribution

This schema comes from SchemaStore, distributed under the Apache License 2.0. Copyright 2015–present Mads Kristensen and contributors. View the original file. The field table and audit on this page are generated by JSONTools.tools; the schema itself is unmodified.

← All schemas