--- title: "Using Is Native File Function" slug: "using-is-native-file-function" updated: 2025-11-11T21:40:46Z published: 2025-11-11T21:40:46Z --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.revealdata.com/llms.txt > Use this file to discover all available pages before exploring further. # Using Is Native File Function Creating a field to add additional natives to a document record. The ***Is Native File*** function when creating a field allows you to upload additional natives to records. This can be particularly useful when trying to examine documents containing more than 500MB of text. > [!NOTE] > Note > > For performance reasons, there is a native file processing limit of 500MB, and a hard limit of 16MB expanded text size for indexing documents in text-based document sets. While settings in Review Manager may be set to indicate a larger limit, any document exceeding the 16MB limit will not be indexed and an error will appear in the indexing log. We strongly recommend contacting [Reveal Support](mailto:support@revealdata.com) if encountering this limitation. > [!NOTE] > Note > > The native and text file sizes differ from the expanded file sizes. The expanded file size is the size of the text set created. ## **Create the Field** 1. Log into Review Manager with an Administrator account. 2. Expand the **Project Setup**pane in Review Manager. 3. Open **Fields**. 4. Use **New Field** to create a new field with the **Is Native File Field** setting selected. This allows native documents to be moved into the field. ![Native File Workflow-01](https://5796933.fs1.hubspotusercontent-na1.net/hub/5796933/hubfs/DOCUMENTATION/ARTICLE%20SCREENSHOTS/Native%20File%20Workflow-01.png?width=519&quality=high) 5. See [***How to Load Data - Third Party Production***](/reveal/docs/load-data-third-party-production) for further details on this modal. ## Populate the field with natives. 1. Import the natives via load file, the same way you would load to the ***Exported Native File*** field. This might require a forced move during Document Import. 2. Prepare a CSV with the BegNum (control number) and path to the added native file, here "*ExtraNative*". ![Native File Workflow-02](https://5796933.fs1.hubspotusercontent-na1.net/hub/5796933/hubfs/DOCUMENTATION/ARTICLE%20SCREENSHOTS/Native%20File%20Workflow-02.png?width=447&quality=high) 3. In Review Manager, open **Import > Documents**. 4. Enter the required information for importing the CSV to your project and select **Force Move** to import the referenced native file to the project's S3 data store. ![Native File Workflow-03](https://5796933.fs1.hubspotusercontent-na1.net/hub/5796933/hubfs/DOCUMENTATION/ARTICLE%20SCREENSHOTS/Native%20File%20Workflow-03.png?width=975&quality=high) ## Check that the file(s) is now in S3. 1. View the contents of the native file field (here *ExtraNative*). ![Native File Workflow-04](https://5796933.fs1.hubspotusercontent-na1.net/hub/5796933/hubfs/DOCUMENTATION/ARTICLE%20SCREENSHOTS/Native%20File%20Workflow-04.png?width=974&quality=high) ## The file can now be exported in a production or downloaded from the viewer. 1. Click on the **Download Native** button to see the new native. ![Native File Workflow-05](https://5796933.fs1.hubspotusercontent-na1.net/hub/5796933/hubfs/DOCUMENTATION/ARTICLE%20SCREENSHOTS/Native%20File%20Workflow-05.png?width=976&quality=high) ## Create a Text Set and reference the new field. This will allow us to view the extra native file in a new viewer. 1. You will notice that there is no "ExtraNative" viewer, as this requires you to create a text set that references the secondary native field as the "load field". 2. In Review Manager, open **Project Setup > Text Sets**. 3. Create a new text set for the added native file field as shown in the illustration below. ![Native File Workflow-06](https://5796933.fs1.hubspotusercontent-na1.net/hub/5796933/hubfs/DOCUMENTATION/ARTICLE%20SCREENSHOTS/Native%20File%20Workflow-06.png?width=954&quality=high) 4. See [***Creating Document Text Sets***](/reveal/docs/create-document-text-sets) for further details on this process. ## Index the New Text Set. 1. This will create the new Text Set viewer for the native in the "ExtraNative" field. 2. Create a list of documents (by control number) containing the addition native file field to be indexed, and save it as a TXT file. 3. In Review Manager, open the **Create** pane. 4. Choose **Indexes**. 5. For your project, select the DocList TXT file and the new text set to be indexed. ![Native File Workflow-07](https://5796933.fs1.hubspotusercontent-na1.net/hub/5796933/hubfs/DOCUMENTATION/ARTICLE%20SCREENSHOTS/Native%20File%20Workflow-07.png?width=969&quality=high) 6. See [***How to Index Data***](/reveal/docs/index-data-1) for further details on this topic. ## Review the New Text Set. 1. Once the text set that references the second native is indexed, you will have a viewer. ![Native File Workflow-08](https://5796933.fs1.hubspotusercontent-na1.net/hub/5796933/hubfs/DOCUMENTATION/ARTICLE%20SCREENSHOTS/Native%20File%20Workflow-08.png?width=974&quality=high) ## Related - [Review Tracking](/review-tracking.md) - [Migration Export – Local Discovery](/migration-export-local-discovery.md) - [Searching Without Leading Wildcard Operators](/searching-without-leading-wildcard-operators.md) - [Migration Import - Reveal](/migration-import-reveal.md) - [Use Translated or Transcribed Text for AI](/use-translated-or-transcribed-text-for-ai.md)