Configure Document Sharing Options on iOS

PSPDFKit has the ability to share documents with other applications and services installed on a device, and it offers a set of APIs to customize the options available to the user when doing so.

You can share any document by tapping the Share button in the navigation bar and choosing what format you’d like to share the document in (where applicable), the page range you’d like to share, and how you’d like to manage the annotations in the document (if any). Once these are specified, you can tap on the Share button at the bottom of the screen.

Sharing Destinations

PSPDFKit 8 for iOS introduces the concept of sharing destinations to use with the revamped PDFDocumentSharingViewController. You can set up sharing destinations — like Mail, Messages, or similar — that define where a document will be sent after the user presses the Share button in the UI.

There are six destinations built into PSPDFKit that you can use out of the box:

Destination Behavior
.activity Shares to a standard UIActivityViewController instance. This is the default destination.
.export Shares to UIDocumentPickerViewController.
.messages Shares to with the resulting files as attachments. Requires the ability to send attachments.
.email Shares to with the resulting files as attachments. Requires to be installed and configured correctly on the device.
.otherApplication Shares to a standard UIDocumentInteractionController.
.print Starts a printing operation via UIPrintInteractionController.

To choose a destination to share to, create a DocumentSharingConfiguration instance and set the destination property on its builder to your preferred destination. Then set that configuration on your PDFDocumentSharingViewController’s sharingConfigurations property.

Note that a single sharing view controller instance can hold multiple destinations at the same time, and the destinations that are available will be displayed in a segmented control on the top of the view controller:

let configurations = [
    DocumentSharingConfiguration.defaultConfiguration(forDestination: .activity),
    DocumentSharingConfiguration.defaultConfiguration(forDestination: .print)

let sharingController = PDFDocumentSharingViewController(documents: [document])
sharingController.sharingConfigurations = configurations
NSArray<PSPDFDocumentSharingConfiguration *> *configurations = @[
    [PSPDFDocumentSharingConfiguration defaultConfigurationForDestination:PSPDFDocumentSharingDestinationActivity],
    [PSPDFDocumentSharingConfiguration defaultConfigurationForDestination:PSPDFDocumentSharingDestinationPrint]

PSPDFDocumentSharingViewController *sharingController = [[PSPDFDocumentSharingViewController alloc] initWithDocuments:@[document]];
sharingController.sharingConfigurations = configurations;

Only one configuration per destination is allowed.

Sharing Configurations

A sharing configuration (see DocumentSharingConfiguration’s API documentation) object defines the set of options available for sharing documents. These include file formats, page selection abilities, annotation processing preferences, the target destination, and more:

let customConfiguration = DocumentSharingConfiguration {
    $0.destination = .export
    $0.fileFormatOptions = [.PDF]

sharingController.sharingConfigurations = [customConfiguration]
PSPDFDocumentSharingConfiguration *customConfiguration = [PSPDFDocumentSharingConfiguration configurationWithBuilder:^(PSPDFDocumentSharingConfigurationBuilder *builder) {
	builder.destination = PSPDFDocumentSharingDestinationExport;
	builder.fileFormatOptions = PSPDFDocumentSharingFileFormatOptionPDF;
	builder.annotationOptions &= ~PSPDFDocumentSharingAnnotationOptionEmbed;

sharingController.sharingConfigurations = @[customConfiguration];

The example above defines a configuration object that will allow a user to export the documents in PDF format. The fact that the .embed option is being removed from the annotationOptions property means the user won’t be able share a PDF with editable annotations, and the UI will only present the remaining annotation options (flatten, remove, summary).

In this example, the default selected option for how to handle annotations (DocumentSharingConfiguration.AnnotationOptions) is inferred in order of relevance, which is defined as follows:

If one option isn’t available, the next one becomes the default one selected when the view controller is presented.

The file format options behave differently, as the default selected option will be determined by the context of the documents being shared.

  1. If the document is an image (ImageDocument) and .image is available, .image will be the option selected by default.

  2. If the document has an original file set and .original is available, .original will be the option selected by default.

  3. For every other condition, .PDF will be the option selected by default.

The default selected options can be updated via the selectedAnnotationOption, selectedFileFormatOption, and selectedPageSelectionOption properties on PDFDocumentSharingViewController.

By default, a PDFDocumentSharingViewController instance will have only one configuration set on its sharingConfigurations property. This default configuration has the destination .activity and all configuration options enabled.

Preconfigured DocumentSharingConfiguration instances can be obtained by calling DocumentSharingConfiguration.defaultConfiguration(forDestination:).

Setting a default set of sharing configurations can be done directly on the PDFConfiguration object you use to instantiate your PDFViewController:

let controller = PDFViewController(document: document) {
    $0.sharingConfigurations = [customConfiguration]
PSPDFConfiguration *configuration = [PSPDFConfiguration configurationWithBuilder:^(PSPDFConfigurationBuilder *builder) {
    builder.sharingConfigurations = customSharingConfigurations;

PSPDFViewController *controller = [[PSPDFViewController alloc] initWithDocument:document configuration:configuration];

Option Sanitization

PDFDocumentSharingViewController will also perform some sanitization of the passed configurations to make sure the provided options are compatible with the documents being shared. In some cases, it may also perform some adjustments.

For instance, the following sharing configuration specifies that a subrange of the document’s pages will be shared to a UIActivityViewController:

let directPrintingConfiguration = DocumentSharingConfiguration {
	$0.destination = .activity
	$0.fileFormatOptions = [.PDF]
	$0.annotationOptions = [.flatten]
	$0.pageSelectionOptions = [.range]
PSPDFDocumentSharingConfiguration *directPrintingConfiguration = [PSPDFDocumentSharingConfiguration configurationWithBuilder:^(PSPDFDocumentSharingConfigurationBuilder * builder) {
	builder.destination = PSPDFDocumentSharingDestinationActivity;
	builder.fileFormatOptions = PSPDFDocumentSharingFileFormatOptionPDF;
	builder.annotationOptions = PSPDFDocumentSharingAnnotationOptionFlatten;
	builder.pageSelectionOptions = PSPDFDocumentSharingPagesOptionRange;

Given the above configuration:

  • When sharing a single-page document, the pageSelectionOptions property from the sharing configuration will be internally overridden to behave as the .all option, because, for single-page documents, there’s no possible range to export other than [0, 1].

  • When sharing a multiple-page document, the shareablePageRange property on the sharing view controller needs to be manually set to a valid range that fits within the available pages of the document being shared.

This kind of sanitization happens for the file format, page selection, and annotation options. Below is a table with the breakdown of what will happen with the options you provide on a variety of cases.

For DocumentSharingConfiguration.FileFormatOptions:

Case Behavior
The documents being shared don’t contain original files associated with them. .original will be removed from the passed options if it was provided.
The PSPDFKit license doesn’t contain the Image Documents product. .image will be removed from the passed options.

For DocumentSharingConfiguration.PageOptions:

Case Behavior
Sharing a single-page document. Ignores whatever value was passed and uses .all.
Sharing multiple documents at once, sharing multiple single-page documents, or sharing multiple documents when at least one of them is an image. Removes .current and .range from the available options.
Sharing one or more documents as images, and the total page count is greater than 20. Removes .all and .annotated from the available options.

Please note that for the page selection options, the cases described above aren’t mutually exclusive. For instance, sharing 21 ImageDocument instances as images complies with both the second and third cases above. This means that all options will be removed, leaving the sharing configuration in an invalid state.

For DocumentSharingConfiguration.AnnotationOptions:

Case Behavior
The current license doesn’t have Annotations enabled. Defaults to .flattenForPrint if present on the available options. Otherwise, defaults to .embed.

When sharing, make sure that after the rules above have been applied to the options, there’s at least one option remaining for each category. Otherwise, the sharing flow will assert.

Presenting the UI

Once the sharing view controller instance has been updated with the desired configuration, call present(from:sender:) to show the UI:

sharingController.delegate = self
sharingController.present(from: self, sender: sender)
sharingController.delegate = self;
[sharingController presentFromViewController:self sender:sender];

When present(from:sender:) is called, the sharing view controller will review its configurations and decide whether or not it’s appropriate to show the sharing option picking UI. If it isn’t, the files will be generated immediately and the final destination UI will be shown instead of the standard configuration UI.

The following example illustrates this:

@objc func customPrintButtonTapped(sender: Any) {
    let directPrintingConfiguration = DocumentSharingConfiguration {
        $0.destination = .print
        $0.fileFormatOptions = [.PDF]
        $0.annotationOptions = [.remove]
        $0.pageSelectionOptions = [.all]

    let sharingController = PDFDocumentSharingViewController(documents: [document])
    sharingController.sharingConfigurations = [directPrintingConfiguration]
    sharingController.present(from: self, sender: sender)
- (void)printButtonTapped:(id)sender {
    PSPDFDocumentSharingConfiguration *directPrintingConfiguration = [PSPDFDocumentSharingConfiguration configurationWithBuilder:^(PSPDFDocumentSharingConfigurationBuilder * builder) {
        builder.destination = PSPDFDocumentSharingDestinationPrint;
        builder.fileFormatOptions = PSPDFDocumentSharingFileFormatOptionPDF;
        builder.annotationOptions = PSPDFDocumentSharingAnnotationOptionRemove;
        builder.pageSelectionOptions = PSPDFDocumentSharingPagesOptionAll;

    PSPDFDocumentSharingViewController *sharingController = [[PSPDFDocumentSharingViewController alloc] initWithDocuments:@[self.document]];
    sharingController.sharingConfigurations = @[directPrintingConfiguration];
    [sharingController presentFromViewController:self sender:sender];

The code sample above creates a sharing configuration that has single options for all categories (PDF, remove annotations, all pages), and has the print destination set. Since there are no options to choose from in this scenario, the option picking UI will be skipped entirely, and the printing interface will be shown instead.

Furthermore, you can call commitWithCurrentConfiguration() on your PDFDocumentSharingViewController instance to take whatever is currently selected on the current configuration, generate the appropriate files, and send them to the appropriate destination in a single step.

Customizing the Sharing Flow

The PDFDocumentSharingViewControllerDelegate protocol offers a comprehensive set of callbacks that let you customize the sharing process.

For instance, here’s how to change the file names for the documents being shared:

func documentSharingViewController(_ shareController: PDFDocumentSharingViewController, filenameForGeneratedFileFor sharingDocument: Document, destination: DocumentSharingConfiguration.Destination) -> String? {
    return "NewName"
- (NSArray<PSPDFFile *> *)documentSharingViewController:(PSPDFDocumentSharingViewController *)shareController willShareFiles:(NSArray<PSPDFFile *> *)files {
    NSMutableArray<PSPDFFile *> *newFiles = [NSMutableArray arrayWithCapacity:files.count];

    [files enumerateObjectsUsingBlock:^(PSPDFFile * file, NSUInteger idx, BOOL * _Nonnull stop) {
        if (!file.fileURL) {

        NSFileManager *fileManager = NSFileManager.defaultManager;
        NSURL *tempFile = [[fileManager temporaryDirectory] URLByAppendingPathComponent:@"NewName.pdf"];

        NSError *copyError;
        [fileManager copyItemAtURL:file.fileURL toURL:tempFile error:&copyError];

        if (copyError) {

        PSPDFFile *newFile = [[PSPDFFile alloc] initWithName:@"NewName" URL:tempFile data:nil];
        [newFiles addObject:newFile];

    if (newFiles.count == 0) {
        return files;

    return newFiles;

And here’s how to be notified about how far along the file processing is:

func documentSharingViewController(_ shareController: PDFDocumentSharingViewController, preparationProgress progress: CGFloat) {
    updateProgressBar(progress: progress)
- (void)documentSharingViewController:(PSPDFDocumentSharingViewController *)shareController preparationProgress:(CGFloat)progress {
    [self updateProgressBar:progress];

You can even react to the user canceling the sharing of the documents based on how far along in the process they were:

func documentSharingViewController(_ shareController: PDFDocumentSharingViewController, didCancelSharingAt sharingStep: PDFDocumentSharingViewController.Step, with configuration: DocumentSharingConfiguration) {
    switch sharingStep {
    case .configuration:
        // Files hadn't been generated yet.

    case .fileGeneration:
        // Process canceled during the file generation process.

    case .destination:
        // User canceled after files were generated.
- (void)documentSharingViewController:(PSPDFDocumentSharingViewController *)shareController didCancelSharingAtStep:(PSPDFDocumentSharingStep)sharingStep withConfiguration:(PSPDFDocumentSharingConfiguration *)configuration {
    switch (sharingStep) {
        case PSPDFDocumentSharingStepConfiguration:
            // Files hadn't been generated yet.

        case PSPDFDocumentSharingStepFileGeneration:
            // Process canceled during the file generation process.

        case PSPDFDocumentSharingStepDestination:
            // User canceled after files were generated.

There’s much more that can be done via the PDFDocumentSharingViewControllerDelegate protocol, so make sure you take a dive into its documentation.

Modifying the Email Subject

When sharing to the .email destination, the default subject on the mail compose view will be the title of the document that’s being shared.

If you wish to have the email subject be something else, you can update the sharing document’s Title property. Be advised that modifying the Document.title property directly doesn’t save the new value back to the actual PDF file, and this will only affect the current instance of the document you’re working with.

To update the document’s title and make sure the changes are saved into the actual document (not just the in-memory instance), you can use the PDFMetadata class. You can learn more about updating a PDF’s metadata in our Customizing Document Metadata guide.


Printing in the context of the sharing workflow can be achieved in two main ways:

  • By specifying .print, or

  • By specifying .activity and then selecting the print action in the system activity view controller UI.

When using the second option, it’s important to note that UIActivityViewController doesn’t provide PSPDFKit with any opportunity to preprocess the PDF for printing.

The document is handed to the iOS printing service, where native iOS PDF support is used to interpret the document and issue printing commands. This might result in printing-related annotation visibility flags not being honored correctly, and in annotations appearing slightly different on printed pages compared to how they look when rendered inside PSPDFKit.

To achieve the best printing results, it’s recommended you flatten the document for printing before it’s sent to the native printing UI. This can be achieved using the .flattenForPrint annotation option, which is included by default when using .print.

Please note that the document can disable printing altogether, in which case the UIActivityTypePrint activity will be removed from the available activities when sharing to .activity, and .print will become unavailable.