---
title: autosavesInPlace
framework: appkit
role: symbol
role_heading: Type Property
path: appkit/nsdocument/autosavesinplace
---

# autosavesInPlace

A Boolean value that indicates whether the document subclass supports autosaving in place.

## Declaration

```swift
nonisolated class var autosavesInPlace: Bool { get }
```

## Return Value

Return Value true if the receiver supports autosaving in place; false otherwise.

## Discussion

Discussion The default implementation of this method returns false. You can override it and return true to declare that your subclass of NSDocument can do autosaving in place. You should not invoke this method to find out whether autosaving in place is actually being done at any particular moment. You should instead use the NSDocument.SaveOperationType parameter that the system passes to your overrides of save and write methods. AppKit invokes this method at a variety of times, and not always on the main thread. For example, autosave(withImplicitCancellability:completionHandler:) invokes this method as part of determining whether the autosaving will be performed in place (NSDocument.SaveOperationType.autosaveInPlaceOperation) or in a separate autosave directory (NSDocument.SaveOperationType.autosaveElsewhereOperation). As another example, the canClose(withDelegate:shouldClose:contextInfo:) method and the NSDocumentController machinery for handling unsaved changes at app termination time both invoke this method as part of determining whether alerts about unsaved changes should be presented to the user.

## See Also

### Configuring the Autosave Behavior

- [autosavesDrafts](appkit/nsdocument/autosavesdrafts.md)
- [preservesVersions](appkit/nsdocument/preservesversions.md)
- [autosavedContentsFileURL](appkit/nsdocument/autosavedcontentsfileurl.md)
- [autosavingFileType](appkit/nsdocument/autosavingfiletype.md)
- [autosavingIsImplicitlyCancellable](appkit/nsdocument/autosavingisimplicitlycancellable.md)