Have you been missing being able to have UI Prefab instances inherit their size (and/or other properties) from the Prefab Asset? Then read on. Prefabs in Unity have a concept of "default overrides" that ensured you could for example use Revert All on a Prefab instance but still have the instance stay at its unique position in the world. This was always the case in Unity, and the 2018.3 Prefab improvement didn't change that so far. From the manual: However, it is sometimes problematic that these properties can't be reverted at all. Particularly for UI Prefabs, many people have found it bad for their workflows that the size of UI Prefabs instances cannot inherit from the Asset. We now have an experimental build that addresses this that we'd like you to try and tell us what you think: DOWNLOAD: https://beta.unity3d.com/download/0bc89d8a1870/public_download.html Changes in this build: Scale is now a default override too (it was the only property on root Transforms that weren't a default override before). More on that below. Default overrides can now be applied or reverted via right clicking on the property or using the component context menu. They will still not be affected by Revert All and Apply All in the Overrides dropdown. Default overrides are now marked in bold again (like they were prior to 2018.3). This is necessary since it needs to be possible to see if they are overridden or not. All root Transform properties are still overrides by default when instantiating a Prefab. It's up to you to revert those of them that you want to be synced with the Prefab Asset. (We know there has been requests to be able to customize which properties are default overrides out of the box, but this is too big a change to consider for now.) So for example, for a UI Prefab instance which has a fixed size that doesn't stretch with its parent, you may want to revert the Width and Height properties to they will receive updates from changes to the Width and Height of the Prefab Asset. While for a UI Prefab instance that does stretch with its parent, you may not want to revert positional fields if the instance is setup to be placed and stretch in a way that's unique to that instance. Why is scale a default override too in this build? It was always a bit subjective which properties should be default overrides. For vehicles you might expect that Revert All should also revert scale, while when placing trees of various sizes, it's less convenient. We've certainly heard requests that scale should be a default override too from some people, but that alone is not the reason. Rather, it's to avoid confusion that could otherwise arise with the new changes. Currently in 2018.3 (not in this experimental build) the root Transform would show up in the Overrides dropdown if its scale was changed but not if any other root Transform property was changed. This was probably ok, since only the scale was bold, so it was not too confusing that only scale would be reverted. However, now that default overrides are bold again, it would be very confusing if for example rotation and scale are both marked bold, but pressing Revert All only reverts scale, and not rotation. By making scale be a default override as well we avoid this problem, since the root Transform will never show up in the Overrides dropdown at all (since changes to default overrides does not cause the component to show up there). The change to make scale a default override is the most disruptive change our of the changes made to default overrides, but we believe it's needed for the other changes to be viable usability wise. Please try out the build and let us know what you think!