Skip to main content
E
Epic_Auto school7375
November 25, 2025
Open for Voting

Add Encoding Options (UTF-8-BOM, UTF-16) for Marker Export to CSV

  • November 25, 2025
  • 2 replies
  • 814 views

Summary: I would like to request an update to the "Export > Markers" dialog that allows users to select the specific text encoding format for CSV files. Specifically, we need options for UTF-8 with BOM and UTF-16.

The Problem: Currently, when exporting markers to CSV, Premiere Pro appears to export in standard UTF-8 without a Byte Order Mark (BOM).

While this is standard for web use, it causes significant issues when opening the CSV files directly in Microsoft Excel (especially on Windows).

Proposed Solution: In the "Export Markers" dialog box, please add a dropdown menu for "Encoding" next to the File Type selector.

Desired Options:

  • UTF-8 (Default)

  • UTF-8 with BOM (Excel Friendly)

  • UTF-16 LE/BE

This small change would save a massive amount of time for editors and assistants who rely on marker lists for deliverables, translation, and producer feedback.

Thank you for considering this request!

    2 replies

    A
    Ahmet26047475ozev
    Inspiring
    January 6, 2026

    @Stan Jones 

    Is there any update on an update to fix marker exports back to the way it originally was without needing to downgrade Premiere? Or at least give export options?

     

    I'm on latest version of Excel so the workaround you gave is a bit iffy, sometimes it works sometimes not and I don't know why.

    Stan Jones
    Community Expert
    Stan JonesCommunity Expert
    Community Expert
    November 25, 2025

    @Epic_Auto school7375,

     

    Upvoted. It is easier to double-click to open in excel. Note that I am running Excel 2013.

     

    What I see, though, is that the new PR export is UTF-8-BOM (25.6.2 and Beta 26.0.0.39) and the old (24.6.5) is UTF-16 LE BOM. A double-click opens UTF-16 LE in Excel as columns, while it opens UTF-8-BOM as a single column.

     

    I am Win11, and I wonder if operating system (particularly mac vs PC) can effect what PR exports and/or how Excel opens it.

     

    A workaround is to open a new book or sheet in Excel, then Data -> Get External Data -> From Text. The text import wizard in Step 1 shows file origin as "65001: Unicode (UTF8)," and a single column. Pick Delimited here, and "My data has headers." In Step 2, use Tab, not comma. You can click Finish here, or set Data Format for each column in Step 3.

     

    Doing the same with a UTF-16 LE BOM file shows file origin as ANSI (Windows), but otherwise works the same.

     

    Stan

     

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices