Do You Need a 1TB iPad Pro? Memory, Project Files, and Backups

In this story

How to Read the M5 iPad Pro Spec Sheet
Check your current iPad storage usage—don’t be misled by the numbers
How Size, Pixels, and DPI in Canvas Information Affect Your Capacity Assessment
How Layer Limit, Used, and Available Answer Memory Requirements
Time-lapse Settings and File Size: How Recording Habits Affect Storage Decisions
What External Storage Can and Cannot Do
Connection Prerequisites and Power Supply Limitations
Compatible Formats and Single Data Partition Requirement
Scope of Supported Apps and File Access Methods
External Storage Cannot Replace Built-in Storage or Memory
Sync and Backup: What iCloud and Computer Backups Do and Do Not Protect
What iCloud Backup Includes and Does Not Include
What Computer Backup Includes and Does Not Include, and the Significance of the Encryption Option
How to Separately Verify Independent, Recoverable Copies for Synced Data and Local Projects
How Export Formats Affect Your Project Recoverability
Native Format and PSD: What Can Be Fully Preserved, and What Is Only a Best Effort
The Trade-offs of Flattened Formats: What JPEG, PNG, and TIFF Each Preserve
Layer Sharing and Target Applications: The Boundary Conditions of Export Behavior
What Information Is Retained and What Is Lost When Archiving Copies
Copying iCloud Drive Files: Hidden Conditions for Optimized Files and Sharing Permissions
Exporting Photo Originals: The Relationship Between External Devices and Local Capacity
Shared Album Copies: Loss of Resolution, Comments, and Likes
Returning to the iPad Capacity Decision: Actual Copying Needs May Differ from Daily Cloud Browsing

How to Read the M5 iPad Pro Spec Sheet

The storage options for the M5 iPad Pro correspond to different CPU and memory configurations, so you need to compare them line by line when making a purchase. Based on Apple’s official iPad Pro technical specifications verified on September 10, 2026, we have sorted out the hardware thresholds among the four versions: 256GB, 512GB, 1TB, and 2TB [1]. This section does not involve any real-world test data or pricing information; it only addresses what the spec sheet itself tells you.

Let’s start with the most critical part: the chip. All M5 iPad Pro models feature the M5 chip, a unified 10-core GPU, a unified memory bandwidth of 153GB/s, and identical descriptions for the media engine [1]. This means that, based on the spec sheet, the four storage versions share the same baseline parameters for graphics processing and memory throughput. However, the CPU core count and unified memory capacity are tiered. The 256GB and 512GB versions come with a 9-core CPU, consisting of 3 super cores and 6 efficiency cores, and 12GB of unified memory [1]. The 1TB and 2TB versions come with a 10-core CPU, consisting of 4 super cores and 6 efficiency cores, and 16GB of unified memory [1]. In other words, if you care about that extra super core and the additional 4GB of unified memory, the 1TB and 2TB models are the only options that provide these two specifications. It is important to note here that the spec sheet does not provide any percentage figures for actual speed improvements resulting from the additional super core, nor does it explain the extent of the difference 12GB versus 16GB might make in daily use or professional software. We can only confirm that these two hardware parameters are indeed different, but we cannot translate this into a specific performance ratio.

Next is the camera and video recording section, another easily overlooked point of differentiation. All four storage versions support ProRes video recording, but the maximum resolution and frame rate are not the same. The 512GB, 1TB, and 2TB versions support ProRes recording up to 4K at 30 fps, while the 256GB version’s maximum specification is 1080p at 30 fps [1]. If you need to record ProRes video at 4K 30 fps directly to the iPad Pro’s internal storage, the 256GB version is not within that range. However, a point of potential confusion needs clarification: although the 512GB version has 12GB of unified memory, placing it in the same tier as the 256GB model, its ProRes recording specification aligns it with the 1TB and 2TB versions, all of which support 4K at 30 fps [1]. Therefore, you cannot infer that its video capability is also capped at 1080p just because its memory specification is the same as the 256GB model. The spec sheet explicitly places the 512GB model in the 4K ProRes camp, so you do not need to assume that a 1TB model is required for this recording specification when making a purchase.

The choice of display surface treatment is also tied to storage capacity. The nano-texture glass is only available as an option for the 1TB and 2TB versions; it cannot be selected for the 256GB and 512GB models [1]. This does not mean all 1TB and 2TB models are forced to use nano-texture; it is merely an option, and users can still choose the standard glass. If you specifically want to select the nano-texture glass, the storage capacity starting point is 1TB.

One more detail worth noting is that both sizes—the 11-inch and 13-inch models—offer these four storage versions, and all the configuration differences mentioned above are tied solely to storage capacity, not to screen size [1]. So, whether you choose the larger or smaller screen, the CPU core count, memory capacity, ProRes recording limit, and the availability of nano-texture all depend entirely on whether the storage capacity you select is 256GB, 512GB, 1TB, or 2TB.

Finally, it should be noted that the media engine description on the spec sheet is identical for all storage versions, but one cannot assert from this that their actual speeds in video export or rendering tasks are exactly the same. A consistent feature list for the media engine is a different matter from sustained real-world performance, and we have no test data to support any conclusions about speed. Similarly, regarding whether the extra memory definitively provides the capacity to handle more layers or more complex projects, the spec sheet itself offers no quantitative explanation, and we will not make such inferences.

This section does only one thing: it lays out, point by point, the hardware differences among the four M5 iPad Pro storage versions as they appear on the official spec sheet. When you are looking at this configuration table, you can clearly see that the dividing line for CPU core count and unified memory is between the 512GB and 1TB models, the threshold for ProRes 4K recording is between the 256GB and 512GB models, and the entry requirement for nano-texture is set at 1TB. These three lines do not overlap. When making a purchase, you need to match the storage capacity to the specifications you actually value, rather than broadly assuming that a larger capacity means a higher tier in every dimension.

Check your current iPad storage usage—don’t be misled by the numbers

Before deciding how much storage to choose for a new iPad Pro, first get a clear picture of how much space you’re actually using right now. This step is more complicated than many people assume. The storage breakdown shown in Settings on iOS and iPadOS does not align with the categories presented in Finder on a Mac or the Apple Devices app on Windows. Directly comparing numbers from the two can easily lead to wrong conclusions [2].

The most straightforward way to check is on the device itself. Go to Settings > General > [Device] Storage, and you’ll see a usage bar broken down by content type, along with a list showing how much space each app occupies [2]. This interface groups content into several categories. Apps includes installed applications and their content, as well as files in the “On My iPhone/iPad” directory within the Files app and Safari downloads. Photos covers photos and videos in the Photos app. Media includes music, videos, podcasts, ringtones, and voice memos. Mail covers emails and attachments. Apple Books includes books and PDFs in the Books app. Messages covers messages and attachments. iCloud Drive includes iCloud Drive content that has been downloaded locally to the device [2]. A key detail here is that iCloud Drive in this tally only counts files already downloaded to the device locally, not all the data stored in iCloud [2]. When buying a new iPad, you should separately note which files need to remain local and which only need to be accessible over the internet. Don’t treat your cloud storage quota as if it were your device usage.

The system interface also lists two categories called “System” and “Other.” System is the space taken up by the operating system, and it varies by device and model [2]. Other contains non-removable mobile resources such as Siri voices, fonts, dictionaries, non-removable logs and caches, Spotlight indexes, and system data like Keychain and CloudKit databases [2]. This portion cannot simply be counted as personal material. System space changes over time, so you can’t treat a single reading as a fixed overhead.

When you connect your iPad to a Mac and view it in Finder, the storage categories change. Finder divides content into Audio, Video, Photos, Apps, Books, Documents & Data, Other, and Synced Content [2]. Here, “Audio” includes songs, audio podcasts, audiobooks, voice memos, and ringtones. “Video” includes movies, music videos, and TV shows. “Photos” includes the photo library, Camera Roll, and Photo Stream. “Apps” lists only installed applications, while “Documents & Data” lists in-app content, including Safari offline reading lists, files stored within apps, and items like contacts, calendars, messages, and emails with their attachments [2]. This categorization logic is entirely different from the device side. For example, the device lists Mail as its own category, whereas Finder places it under “Documents & Data.” If you’re used to checking storage reports on a computer, you need to be aware that the numbers you see there and the numbers shown in iPad Settings come from two different classification systems and cannot be directly mapped to each other.

What requires even more attention is how cached files are handled. Finder and the Apple Devices app classify cached music, videos, and photos as “Other” storage [2]. These cached files are automatically generated by the system when you stream or view content, with the purpose of loading faster the next time you access them. When device storage runs low, the system automatically deletes these cached files to free up space; users do not need to manually clear them [2]. Precisely because Finder puts caches into “Other” while the device may place them into the corresponding media categories, the music or video usage shown on the two sides can be inconsistent [2]. If you notice that “Other” on your Mac appears much larger than on your iPad, don’t immediately assume there are abnormal files—this is very likely just a discrepancy caused by how caches are categorized. Apple explicitly states that if the storage shown on the device does not match what appears in Finder or the Apple Devices app, the device’s own reading under Settings > General > [Device] Storage should be treated as authoritative [2].

Another easily confused point is “Synced Content.” Finder has a category called “Synced Content,” which refers to media content transferred from your computer to the iPad through the sync function [2]. This type of data cannot be deleted directly on the iPad. To remove it, you must go back to Finder on the computer or the Apple Devices app, uncheck the corresponding content, and sync again [2]. If you can’t find the source of certain space usage in the iPad’s storage interface, check the sync settings on the computer side to see whether a large amount of old synced content remains on the device.

When taking stock of your current usage, there are several boundaries to keep in mind. Caches and temporary data may not be counted toward usage on the device side [2], which means the space an app appears to occupy may not include all the temporary files it generates. If you tap into an app’s detail view, the system may show the size of that app’s documents and data, but cached data may not be included [2]. For this reason, you cannot simply add up the displayed usage of all apps and assume that equals the total usage; there may be a gap between the two caused by caches.

Finally, it needs to be made clear that this section only discusses how to read the storage usage numbers on your current device. It does not cover any deletion operations or cleanup advice. You don’t need to decide at the inventory stage what to delete and what to keep. You only need to accurately understand what each number represents, where the differences between various interfaces lie, and which portions of usage you can address by purchasing a larger capacity versus which are system overheads that will exist no matter what. Armed with this information, when you look at the capacity options for a new iPad, you’ll be able to judge whether 256GB, 512GB, 1TB, or 2TB can cover the local space you actually need, rather than being misled by your total iCloud capacity or the “Other” number in Finder.

How Size, Pixels, and DPI in Canvas Information Affect Your Capacity Assessment

When you open the Canvas Information interface in Procreate, you see a set of precise technical parameters that directly relate to the storage footprint and memory requirements of your future work. By entering Canvas Information under the Actions menu, you will see that the Dimensions area lists pixel width and height, physical width and height, and the DPI value [3]. These fields describe the canvas size; for the actual file size, refer separately to Total file size.

Pixel width and height represent the actual number of pixel points the canvas contains, and this is the core variable affecting file size. Physical width and height are the units chosen when creating the canvas, such as millimeters or inches, and they are calculated together with DPI [3]. If you set the dimensions directly in pixels when creating the canvas, Procreate will calculate the physical size in reverse using the DPI, and the default physical unit used depends on your geographic region [3]. This means that when comparing the storage footprint of different works, you should focus on pixel dimensions rather than physical dimensions, because the latter is merely a conversion result for printing or display.

The role of DPI here needs to be understood accurately. DPI stands for dots per inch, a print resolution metric that tells you how many pixels are distributed per inch of canvas [3]. The official handbook explicitly states that changing the DPI setting alters the physical size of the canvas but does not change the pixel dimensions [3]. Therefore, when comparing existing works, first ensure the pixel dimensions are consistent; you cannot infer which iPad tier is needed based solely on the print DPI level.

The Canvas Information interface also provides a Total file size field, which displays the volume of the current .procreate file in MB [3]. This figure is the most direct basis for judging storage requirements. If you have completed work files on hand, you can check their total file sizes one by one and add them up to obtain the local space occupied by your existing portfolio. When you do not yet have actual project files, you should not use unverified layer counts to extrapolate a definite file size.

How Layer Limit, Used, and Available Answer Memory Requirements

The Layers area in Canvas Information displays three key figures: the maximum layer count, the used layer count, and the available layer count [3]. These three figures are your direct reference when deciding whether you need more unified memory during purchase, because they directly reflect how many more layer operations the current canvas can support under hardware constraints.

The maximum layer count is the upper limit available for the current canvas. The Crop and Resize interface will display the layer count corresponding to the new canvas dimensions, and there are hardware limitations [3]. This handbook does not contain a layer count comparison across M5 capacity tiers; therefore, you need to verify the same canvas on the target device and app version, and you cannot guarantee a specific improvement based solely on the two figures of 12GB and 16GB.

The used layer count tells you how many layers have already been created in the current canvas, and the available layer count is the result of subtracting the used layer count from the maximum layer count [3]. These two figures can help you assess your actual layer count needs based on your working habits. If you review completed works on your existing device and find that the available layer count is frequently near zero, it indicates that your creative workflow demands a very high number of layers and often hits the hardware limit. In this case, you should first verify the actual maximum layer count the target model can provide before judging whether an upgrade will solve the problem. If your available layer count is consistently ample, it means the current memory configuration already meets your layer usage habits, and the increase in the layer limit brought by additional memory will have limited impact on your actual creation.

Canvas Information also lists the usage counts for Assist, Clipping Masks, Masks, and Layer Groups [3]. These layer types also consume memory resources, but the official documentation does not specify their memory consumption conversion ratio relative to standard layers. Record the used and remaining values given in the interface, and avoid adding different categories together repeatedly.

Time-lapse Settings and File Size: How Recording Habits Affect Storage Decisions

The Video settings area provides information on the time-lapse video's length, quality, resolution, file size, and codec [3]. These parameters directly tell you how much additional storage space recording the painting process will consume and which settings you can adjust to control this consumption.

The Video file size field displays the current volume of the time-lapse video in MB [3]. This figure will grow as you continue painting; it is not a fixed value. The official handbook explains that video length, quality settings, and resolution all affect file size [3]. Higher quality settings yield better visual quality but result in larger file volumes, consuming more storage space and leading to slower uploads and downloads [3]. The same applies to resolution: a higher resolution means the video contains more pixels and looks better on large screens, but the file volume will also be larger [3]. If you habitually record the painting process for long durations while maintaining high quality and high resolution settings, the time-lapse video may become a significant component of storage consumption, and you need to account for this growth space when choosing a capacity tier.

Video length displays the playback duration of the time-lapse video [3]. It describes the playback duration of the exported video; the time the artwork has been open has a separate Tracked time field. Do not conflate these two types of duration [3].

The Video codec field shows the compression type used for the video [3]. You may record this field, but this handbook does not provide a comparison of optional codecs and their corresponding sizes, so you cannot infer a fixed compression ratio from it.

When comparing multiple completed works, record Video file size and Total file size separately. They describe different objects, and you should not add the two columns together without verification. How many project files you retain and whether you will also export videos and share files will affect your local capacity needs; actual exported files should be verified independently.

What External Storage Can and Cannot Do

Before considering 256GB, 512GB, 1TB, or 2TB, you need to understand how external storage actually works with iPad Pro. External storage can expand the total amount of files you can access, but its operating logic is entirely different from that of built-in storage. This section only discusses the prerequisites for connecting external storage, compatible formats, power supply requirements, and the range of supported apps, helping you assess to what extent external storage can supplement the capacity you choose.

Connection Prerequisites and Power Supply Limitations

Connecting a USB drive or SD card reader to iPad Pro requires plugging it into the charging port via a compatible connector or adapter [4]. The specific adapter needed depends on your iPad model and the external device itself. The situation is different if your iPad Pro is equipped with Thunderbolt or USB 4 ports. Such models support connecting multiple USB drives and other Thunderbolt devices in a daisy chain, then connecting the entire device chain to the iPad's charging port [4]. This means you can mount multiple storage devices simultaneously, but only if your iPad Pro is a model that supports Thunderbolt or USB 4. If you are unsure whether your model supports this, you need to verify this specification in Apple's technical specifications; you cannot assume this capability based solely on the port's physical appearance as USB-C.

Power supply is another hardware requirement that is easily overlooked. External hard drives typically require an external power source when connected to iPad [4]. If your iPad Pro supports Thunderbolt or USB 4 and the external hard drive itself does not provide independent power, you can use a powered USB hub to resolve the power supply issue [4]. This means that if you plan to use an external hard drive while on the go, you will need to carry additional power supply equipment, and the portability of the entire setup is significantly different from using built-in storage directly.

Compatible Formats and Single Data Partition Requirement

For an external storage device to be recognized by iPad, it must meet two conditions: it must have only a single data partition, and it must be formatted as one of the following file systems: APFS, APFS (encrypted), macOS Extended (HFS+), exFAT (FAT64), FAT32, or FAT [4]. Before using an existing hard drive with iPad, you need to verify the drive's partition structure. If the drive already contains data and has multiple partitions, reformatting will erase the content on the target storage, so you must first secure the original data before considering reformatting. Apple's official documentation does not provide complete steps for directly erasing or repartitioning an external hard drive on iPad, only stating that you can use the Files app on iPad or a Mac or PC to change the storage device's format [4]. If you need to perform operations on iPad, you should first check in the Files app whether the current hard drive is recognized, then decide on subsequent actions, but any action involving formatting must be done on the premise that the data has been safely backed up.

When choosing a format, you must also verify compatibility with other devices you use, not just confirm it on the iPad side. For drives that already contain data, first record the format and partition information, then check the requirements of the target device to avoid rushing to format just for the sake of connection.

Scope of Supported Apps and File Access Methods

Files stored on external storage cannot be directly opened in all apps on iPad. Apple explicitly states that you can use the Files app and other supported apps to access files stored on external devices [4]. This means the access point for external storage is the Files app and those third-party apps that explicitly support reading from external storage. You cannot assume that all apps can directly browse files on an external hard drive as they would with built-in storage. For apps centered around project files, such as Procreate, you need to confirm whether it supports directly opening or importing files from external storage, and whether it supports saving projects onto external storage. If an app does not support direct reading from or writing to external storage, you can check the app's import and export methods to see if operations can be completed using local copies. This extra step adds operational links to your workflow and also means you need to reserve sufficient temporary space on the built-in storage to accommodate these files.

The way to view content on external storage is, within a supported app like the Files app, to tap "Browse" at the bottom of the screen, then tap the device's name under "Locations" [4]. If it does not appear under "Locations," you need to tap "Browse" at the bottom again [4]. SD cards can also directly import photos and videos into the Photos app [4], but this is a media import function and is different from using it as working storage.

External Storage Cannot Replace Built-in Storage or Memory

A key distinction needs clarification here. External storage expands the file storage space you can access; it cannot directly increase the built-in storage capacity of iPad Pro, nor can it replace unified memory. App installation locations, system data, and the local caches and temporary files of some apps can still only reside on the built-in storage. You cannot treat an external hard drive as a simple extension of the built-in space and expect all data to automatically flow to the external device. Similarly, external storage and unified memory are entirely different hardware layers. The capacity figure of an external drive cannot prove that the upper limit of application layers has changed; the limitations for a target project must still be verified on the specific device and within the specific app.

If you plan to use external storage to hold completed project files or time-lapse videos to reduce the burden on built-in storage, this approach is feasible. However, you need to accept the premise that these files must be copied back to the iPad locally when editing is required, or you must rely on the app's direct read/write support for external storage. If you frequently need to switch between different projects, the frequent file migration will incur additional time costs. When choosing the iPad Pro storage capacity, you should view external storage as an archiving and expansion solution, not an equivalent replacement for built-in capacity. You need to decide on the built-in storage tier based on the total volume of project files you need to keep locally and readily editable at the same time; external storage addresses the storage of historical projects and exported files.

Sync and Backup: What iCloud and Computer Backups Do and Do Not Protect

Before deciding on the storage capacity for an iPad Pro, you need to clarify a fundamental question: which data on your device is already protected through sync or backup, and which data still exists only on that single machine. This assessment directly affects your need for local capacity. If you rely on iCloud or a computer to "save" your data but mistakenly assume that sync is equivalent to backup, you may discover that certain content cannot be recovered in the event of device failure or accidental deletion. This section, based solely on Apple's official explanations of backup methods, explains what iCloud backups and computer backups each include and exclude, and how to verify whether your data also exists as an independent, recoverable copy [5].

What iCloud Backup Includes and Does Not Include

An iCloud backup is not an exact, unaltered copy of everything on your iPad uploaded to the cloud. Apple explicitly states that an iCloud backup includes information and settings on the device that have not yet been synced to iCloud [5]. The meaning of this statement needs to be unpacked. If some of your data is already stored in the cloud via iCloud's sync function, then that data will not be included in the iCloud backup. Official documentation lists several categories of content explicitly excluded from iCloud backups: notes that have already been stored and synced to iCloud; if you have iCloud Photos enabled, photos are not included in the backup; if you have Messages sync enabled, iMessages, SMS, and MMS messages are also not included in the backup; data stored in other cloud services like Gmail and Exchange is similarly excluded; Apple Mail data, Apple Pay information and settings, Face ID or Touch ID settings, iCloud Music Library and App Store content, as well as offline maps, are also outside the scope of an iCloud backup [5].

This means that if you have iCloud Photo Library enabled, your photos already exist in iCloud through the sync mechanism, and the iCloud backup will not include them again. This is not inherently a problem, but you need to be aware that sync and backup are two different protection mechanisms. Sync means that if you delete a photo on one device, that deletion operation will sync to all devices and to iCloud. If you accidentally delete a photo and do not recover it in time from the Recently Deleted album, sync itself cannot help you retrieve the deleted content. An iCloud backup will not retain an extra copy of your photos just because you have iCloud Photos enabled. Therefore, if you treat iCloud Photos as your sole photo storage solution, you need to confirm whether you accept the deletion risk that comes with sync. If you need a copy that is independent of sync and can be restored to a state at a specific point in time, you must separately verify an independent copy solution; the following text will explain that computer backups also have exclusions.

For creative projects, first distinguish between in-app work items, exported files, and sync directories. Apple's whole-device backup instructions cannot substitute for an app's own save instructions, and you cannot assume all projects are within a sync folder just because you see one.

What Computer Backup Includes and Does Not Include, and the Significance of the Encryption Option

The coverage scope of a computer backup differs from that of an iCloud backup. Apple notes that a computer backup, unlike sync, includes nearly all data and settings on the device [5]. However, exclusions exist here as well. A computer backup does not include content synced from iTunes and the App Store, nor does it include PDFs downloaded directly to Apple Books; it does not include content synced from a Mac or PC, such as imported MP3s, CDs, videos, books, and photos; it does not include data already synced and stored in iCloud, such as iCloud Photos, iMessages, SMS, and MMS messages; it does not include Face ID or Touch ID settings, Apple Pay information and settings, Apple Mail data; nor does it include offline maps [5].

There is a critical detail here concerning Health data, Activity data, and Keychain. Apple explicitly states that if you need to back up this content, you must create an encrypted backup [5]. The encryption option for computer backups is turned off by default [5]. If you do not select the encryption option when backing up your iPad on a Mac or PC, this sensitive data will not be included in the backup. For users who rely on Keychain to store passwords or the Health app to record data, this default-off setting means you need to actively confirm that encryption is enabled before each backup. If you have never manually turned on encrypted backups, your computer backup is likely missing this portion of data.

A computer backup also does not include data already synced through iCloud [5]. This logic is consistent with that of iCloud backups. If your photos are already synced via iCloud Photos, the computer backup will not include them again. Therefore, a computer backup does not automatically provide you with a local copy of your iCloud Photos. If you need a copy of your photos independent of iCloud sync, you need to separately save an independent photo copy to your computer through other means, rather than relying on the backup mechanism.

How to Separately Verify Independent, Recoverable Copies for Synced Data and Local Projects

After understanding the respective scopes of iCloud backups and computer backups, you need to check your critical data one by one to confirm whether at least one recoverable copy exists for each, independent of the current device. "Independent" here means that this copy will not disappear due to sync triggered by a deletion operation on your current device, nor was it never included because of backup exclusion rules.

For photos, if you have iCloud Photos enabled, your photos exist in iCloud via the sync mechanism. But as mentioned earlier, sync itself cannot guarantee recovery after deletion. If you need an independent copy, you can check whether your computer holds an independent copy of the original photo files, or whether you have used another cloud service for a secondary backup. If iCloud Photos is not enabled, you should still verify the scope based on backup type and source, paying particular attention to the fact that content synced from a computer falls under computer backup exclusions.

For app projects, you should verify the export formats supported by the app and whether the output files retain the content needed for subsequent editing. Do not just check thumbnails, and do not treat a notification that the device backup is complete as standalone evidence that each project is recoverable. For projects that need to be preserved, save a copy in another location and verify the open result with a supported app version; keep the original when checking.

Exported videos and original projects should also be documented separately. A playable video does not prove that layers, masks, and editable information are still present; they are different deliverables. First determine what you want to preserve, then check its save location and the applicable backup scope.

Ultimately, choosing 256GB, 512GB, 1TB, or 2TB depends not only on your current total data volume but also on how many independent copies you are willing to maintain for this data and where those copies are stored. If you rely on iCloud sync as your primary means of protection, you need to accept the inherent limitations of the sync mechanism and ensure that critical data has additional independent copies. If you use an encrypted computer backup, you need to confirm that the encryption option is enabled and that backups are performed regularly. If data falls outside sync and backup coverage, check whether any independent copy exists before treating it as protected. In this case, you need to reserve sufficient local capacity for this data until you establish a reliable mechanism for independent copies.

How Export Formats Affect Your Project Recoverability

When you are deciding whether to choose 256GB, 512GB, 1TB, or 2TB of storage for an iPad Pro, an easily overlooked variable is how many editable project files you intend to keep, and what format those files exist in. Procreate’s Share menu offers multiple export formats, and each format retains layers, effects, and editing capability to a completely different degree [6]. This section does not discuss full-device backups; it focuses solely on Procreate’s own export options, explaining the differences in project recoverability across formats and how those differences affect your local storage planning.

Native Format and PSD: What Can Be Fully Preserved, and What Is Only a Best Effort

Procreate’s native .procreate format is the option that the official documentation states can preserve all artwork data. The official handbook explicitly lists that when you export using the .procreate format, all layers, masks, and effects are perfectly preserved, and canvas information is carried along with the file, which allows the person receiving the file to view your signature [6]. Additionally, if you enabled Time-lapse recording on that canvas, the video data is also embedded in the file [6]. This means that when you save a copy of a piece of artwork in the .procreate format, you are keeping a complete, recoverable project file that contains every element needed to continue editing. If you plan to continue modifying old works after switching devices, or need to hand off a project for someone else to continue working on another iPad, the .procreate format matches the official method for complete artwork preservation.

However, there is a hard requirement regarding version compatibility that you need to note. Procreate 5.3 improved the file compression method, and any .procreate file exported from Procreate 5.3 will not open in older versions of Procreate and Procreate Pocket [6]. If you encounter a situation where a .procreate file cannot be opened, the official solution provided is to update to the latest version of Procreate and try again [6]. This limitation means that if you created and exported a project file on an older device using version 5.3 or later, and the recipient or your own other device is still running an older version of Procreate, that file cannot be opened directly. When planning storage copies, you need to confirm that all devices that might open the file have been updated to a compatible version; otherwise, the complete preservation advantage of the .procreate format cannot be realized due to a version barrier.

The PSD format provides another path for retaining editing capability, but its scope of preservation is limited. When Procreate exports a PSD, it preserves layers, layer names, opacity, visibility, and blend modes [6]. The official handbook describes PSD as a great way to send a file with all its layers intact to someone who does not yet own Procreate [6]. This statement defines the applicable scenario for PSD: it is primarily used for cross-software collaboration, not as a full backup of a Procreate project. The official materials only list the attributes preserved above and do not promise that a PSD export can retain masks, effects, Time-lapse video, or canvas information. Therefore, when you export your artwork as a PSD, you obtain an editable file that preserves the layer structure and basic properties, but you cannot assume that all Procreate-specific effects and settings will be fully reproduced in the PSD. If you need a copy that can be worked on further in Photoshop, PSD is a suitable format. But if you need a project backup guaranteed to be fully recoverable in Procreate, the .procreate format is the complete artwork format explicitly stated by the official documentation.

The file sizes of the two formats need to be compared based on actual export results; you cannot guarantee which one is smaller just from the file extension. When keeping a native project and a collaboration copy, record the actual file sizes separately; do not delete an original project that still needs further editing just to save space.

The Trade-offs of Flattened Formats: What JPEG, PNG, and TIFF Each Preserve

When you do not need to retain editing capability and only need a high-quality finished image, Procreate offers three flattened formats: JPEG, PNG, and TIFF. What these three formats have in common is that they all flatten your artwork into a single layer, but they differ in image quality, file size, and specific functionality [6].

JPEG is a lossy format; it flattens your artwork and sacrifices some visual quality in exchange for a smaller file size [6]. The official handbook describes it as a web-ready format and notes that it is one of the most widely supported image formats, making it a universal option for easy sharing [6]. If you need a copy for quick sharing, uploading to the web, or sending via messages, the small file size of JPEG is a clear advantage. But you need to accept the fact that JPEG’s lossy compression means you cannot recover an image quality fully identical to the original canvas from this copy. If you plan to use JPEG as the sole archival format for your artwork, the details in the original canvas have been permanently lost during the compression process.

PNG is a lossless format; it flattens your artwork but preserves the full image quality [6]. The official handbook points out that PNG files are slightly larger than JPEGs but are equally universal and have the significant advantage of preserving transparency [6]. If your artwork contains a transparent background or transparent elements, the official documentation explicitly lists that PNG supports transparency. For icons, stickers, or overlay assets that require a transparent background, you can choose PNG according to the recipient’s requirements. In terms of storage planning, if you have a large number of artworks that need to preserve transparency, PNG will take up more space than JPEG, but this increase is exchanged for lossless quality and transparency information.

TIFF also flattens layers but perfectly preserves image quality [6]. The official handbook explains that exporting with layers would cause the TIFF file size to be excessively large, so Procreate’s TIFF export chooses to flatten the image [6]. TIFF has been used in the printing industry for decades, is compatible with all major software, and is a common choice in professional print workflows [6]. If you need to send your artwork to a print shop or publisher, TIFF is a suitable delivery format. No testing was conducted here on the actual export sizes or full format capabilities of these three formats, so no additional ranking is made.

The common point among these three flattened formats is that none of them preserve layers, masks, effects, or any editable structure. Once you have only kept a JPEG, PNG, or TIFF copy and the original .procreate project is lost, you will be unable to make any layer-level modifications to the artwork. When deciding on storage capacity, you need to distinguish between two types of files: project files for continued editing, and finished images for display or delivery. If you only keep copies in flattened formats, the storage space you need will be relatively smaller, but you lose the original editable layer structure. If you keep both the .procreate project and the flattened export files, you need to reserve two copies’ worth of storage space for the same artwork.

Layer Sharing and Target Applications: The Boundary Conditions of Export Behavior

Procreate’s Share menu also contains a Share Layers section, which provides options to export layers as a multi-page PDF, a folder of PNGs, or animation formats [6]. There is a uniform boundary condition for the behavior of these export methods: regardless of which format you choose, only visible layers will be exported [6]. This means that if you hide certain layers before exporting, those layers will not appear in the export result. This rule applies to all formats under Share Layers, including PDF, PNG, and the animation formats GIF, PNG, and MP4 [6].

Specifically, PDF export merges all visible layers into a single multi-page PDF file, with each layer becoming a separate page [6]. For example, five visible layers result in five pages. PNG export treats each visible layer as an individual PNG file; you will receive a folder containing multiple PNG files [6]. The animation formats treat each visible layer as a single frame in a looping animation; GIF is the most universal and common web animation format, PNG is suitable for animations containing transparent elements, and MP4, while less common than GIF, can produce a smaller file size [6].

The common limitation of these layer-sharing formats is that they only export visible layers, not the full layer structure of the canvas. If you need to preserve complete layer information for future editing, none of the formats under Share Layers can substitute for a .procreate or PSD export. Their design purpose is to distribute layer content in a specific way, not to save a recoverable project file.

The final destination of an exported file depends on the apps installed on your iPad. Once you select an export format, iPadOS’s sharing system is automatically triggered, allowing you to send the file to system functions like AirDrop, Messages, Mail, and Notes, as well as any app linked to the sharing system [6]. The available target apps will vary depending on the apps actually installed on your iPad [6]. This means that whether you can directly export a file to a specific cloud storage or third-party app depends on whether that app is installed and registered with the sharing system. When planning your workflow, you need to confirm whether your commonly used storage destinations are available in the Share menu, rather than assuming all apps can serve as export targets.

For capacity planning, a single artwork might simultaneously leave behind a native project, a collaboration file, and a delivery image. Checking the actual versions, quantities, and save locations you intend to keep separately is more reliable than estimating capacity using only canvas dimensions. Whether sharing is complete should also be verified at the destination; the appearance of an app in the Share menu does not mean the file has been delivered.

What Information Is Retained and What Is Lost When Archiving Copies

When deciding what storage capacity to choose for an iPad Pro, a practical issue you must face is how many usable data copies you plan to keep locally, and whether those copies actually contain all the information you think they do. This section does not discuss the definition of backup, nor does it cover deletion operations. It focuses solely on one specific action: when you copy files, photos, or shared album content from iCloud to another location, which parts of the original data does the copy you receive retain, and which parts does it lose. These differences directly affect how much space you need to reserve on your iPad's local storage for usable copies [7].

Copying iCloud Drive Files: Hidden Conditions for Optimized Files and Sharing Permissions

The operational path for copying files from iCloud Drive to local iPad storage or another cloud service is itself clear. In the Files app on iPad, you can select iCloud Drive under "Locations" in the sidebar, tap "Select," check the files and folders you need, then tap "More" and choose "Copy Items." After that, navigate to "On My iPad" or the location of another cloud service, long-press the target folder, and tap "Paste" [7]. This process appears to simply move files from one place to another, but two key details directly affect whether the copy you receive is complete.

The first detail involves Optimize Storage. Apple's official documentation clearly states that if a file is in an optimized state in iCloud Drive, it will be downloaded to your device before being copied to the new location [7]. This means that when you perform a copy operation, the iPad needs sufficient available local space to temporarily accommodate this downloaded full file before the copy can be completed. If the iPad capacity you chose is already tight and you need to copy a large number of optimized large files, this "download first, then copy" mechanism could exhaust the remaining space during the operation. When planning capacity, you cannot just calculate the space needed to store the final copies; you also need to leave a buffer for the temporary downloads that may occur during the copying process.

The second detail involves shared folders. If you copy files from a shared folder in iCloud Drive to another location, the resulting copy will not carry over the shared access permissions [7]. In other words, you get the file content itself, but the original attribute of being "accessible to multiple people" is stripped away. The access permissions for the new location need to be verified separately. For someone who needs to preserve the collaboration state, this copy cannot restore the original sharing relationships. But for someone who just wants to keep a snapshot of the content, this copy is complete at the content level. You need to judge, based on how frequently you use shared folders and for what purpose, whether you need to reserve local space for these copies stripped of permissions.

There is a boundary here that is easy to overlook: the copy operation in the Files app produces a duplicate; the original file remains in iCloud Drive. The copy and the original no longer have a synchronization relationship afterward. Modifications you make to the copy will not be reflected in the original in iCloud Drive, and vice versa. Copying to "On My iPad" retains a local file; opening it offline still depends on the app and file format. But if you need a working file that continuously stays in sync with the cloud, the copy operation cannot achieve this goal.

Exporting Photo Originals: The Relationship Between External Devices and Local Capacity

The situation with photos is more complex than with files, because the concept of the "original" in iCloud Photos might not be the same as the version you see on your device. If you use iCloud Photos, photos and videos are automatically uploaded to iCloud in full resolution [7]. However, what is stored locally on your iPad might be an optimized version, not the full-resolution original. When you need to export a complete copy of photos to an external storage device, you must first make a key choice in Settings.

The specific steps are: connect the external storage device to your iPad, open "Settings" and tap your name, go into iCloud and select "Photos," then choose "Download and Keep Originals" [7]. After completing this step, you can then select the photos and videos you want to export in the Photos app, tap the share button, choose "Export Unmodified Original," and then select your external storage device as the destination to save them [7].

This instruction provides the operational path of downloading originals and then exporting them, but it does not require you to first download the entire photo library completely, nor does it prove that other methods are unusable. Capacity planning should verify the specific data selected this time and the specific operational conditions; you cannot extrapolate this procedure into a requirement that you must buy an iPad capable of holding your entire cloud photo library.

If you only want to download a small number of photos or videos, iCloud.com offers another path. Access iCloud.com on your iPad, go into Photos, select the photos, and tap download. The photos will be downloaded as a .zip file into the "Downloads" folder of iCloud Drive [7]. You can then move this .zip file to an external storage device in the Files app [7]. This path does not require you to first switch the setting to "Download and Keep Originals," but what it downloads is the "most recent version" of the photos and videos [7]. Official documentation does not state whether this "most recent version" differs from the "Unmodified Original" in resolution or metadata. Therefore, if you have requirements for the absolute integrity of the photos, you should further verify the version you need, rather than inferring from the name "download" that the file contents are completely identical.

Shared Album Copies: Loss of Resolution, Comments, and Likes

Copies from shared albums are another area prone to misunderstanding. When you copy photos and videos from a shared album, the copy you get is not full resolution, and comments and likes information will not be saved [7]. Apple's official documentation explicitly states that when copying photos and videos from a shared album, they are not stored at full resolution, and comments or likes are not stored [7].

This means there is a clear gap between "accessible" and "restoring all information" for copies from shared albums. You can access the image content of this photo, you can save it locally or send it to others, but the pixel count of this photo is lower than the full resolution at the time of the original capture, and all the social interaction information surrounding this photo—who liked it, who left a comment—will not appear in the copy. If you need the full-resolution original, a copy from a shared album cannot meet this requirement. You need to go back to the original photographer to get the original, or confirm whether the original exists in your own iCloud Photo Library.

The impact of this difference on capacity planning is that you cannot use the size of a shared album copy to estimate the storage needs of the full-resolution original. The version in the shared album has been compressed and is smaller in size. If you plan to save a large amount of shared album content locally, the space you need will be less than saving an equivalent number of full-resolution originals. But conversely, if you mistakenly think the shared album copy is the original, and later find you only have a compressed version when you need the full-resolution file, this information gap cannot be remedied by increasing storage capacity.

Returning to the iPad Capacity Decision: Actual Copying Needs May Differ from Daily Cloud Browsing

Putting the three threads above together leads to a conclusion with practical guidance for capacity selection: when you usually browse files, view photos, or flip through shared albums in iCloud, you do not need your iPad's local storage to hold complete copies of all this content. Browsing behavior relies on a network connection and on-demand downloading, putting relatively little pressure on local capacity. But when you decide to perform a copy operation, turning this content into independent copies stored locally or on an external device, the situation is completely different.

When copying iCloud Drive files, optimized files need to be downloaded first before copying; you need to reserve space for this download process. When exporting photo originals, you must first let the iPad download the full-resolution originals, verify the files needed for this operation and the available space; you cannot infer that the entire photo library must be downloaded. When copying shared album content, you get a compressed version, which is smaller in size, but you also need to accept the loss of resolution and social information.

The demand these copy operations place on local capacity is on a different scale compared to the capacity usage during your daily cloud browsing. You cannot use the reasoning "I have 200GB of data in iCloud, and my iPad usually works fine with it" to infer that "choosing 256GB is enough for me." Because "usually works fine" corresponds to browsing mode, whereas copy operations correspond to download mode. The space requirement in download mode depends on how much content you actually want to copy, how much of that content is in an optimized state, and whether you need full-resolution originals.

When deciding between 256GB, 512GB, 1TB, or 2TB, what you need to evaluate is not the total storage amount of iCloud, but how many independent copies you plan to keep locally, and the types of these copies. If you only need to occasionally copy a few files or a few photos, the additional capacity requirement might be very small. If you need to regularly export an entire iCloud Drive folder or the entire photo library as independent copies, then you need to ensure your iPad has enough local space to accommodate the largest download volume in a single operation. This figure needs to be estimated based on your own actual data volume, not by relying on any universal ratio or average.

Mentioned in this story

These links lead to official or retailer pages. We currently earn no affiliate commission from them. Check the destination for regional availability, configuration and pricing.

iPad Pro View official specifications ↗

Sources