Skip to main content
  • EN

We are excited to unveil FME 2025.1, our most powerful release yet, packed with game-changing capabilities first revealed at The Peak, our annual user conference. This release brings the spatial computing power of the FME Platform to the field with FME Realize, and unleashes the full power of All-Data, Any-AI capabilities with FME Data Virtualization. With expanded AI-powered productivity through AI Assist, new multi-language support for global users, and a completely redesigned DocumentPDF Writer, FME 2025.1 is designed to empower every user, team, and organization to work smarter, faster, and more connected than ever before.

Feature Highlights

FME Realize: Bring your digital twins to life with FME Realize, an augmented reality application authored on FME Form and powered by FME Flow. Designed for field crews and mobile teams, it delivers real-time, in-context access to enterprise data, enabling users to visualize, update, and act on live data for inspections or work orders directly in the field. With FME Realize, you can boost productivity and unlock the full value of your digital twin investments.

Learn more about FME Realize and how to get started here.

FME Data Virtualization: FME Data Virtualization is a new capability for the FME Platform that enables you to build secure, AI-ready, OpenAPI-compliant REST APIs directly on top of any system or data source FME supports. It offers CRUD (Create, Read, Update, Delete) functionality with built-in caching and security, all through a no-code interface. 

Learn more about FME Data Virtualization and how to get started here. 

AI Assist: AI Assist is your built-in, context-aware FME expert that offers instant, reliable guidance by drawing from trusted sources, such as documentation, community posts, and Knowledge Base articles. It understands your workspace context and helps you learn features, troubleshoot issues, and build workflows faster, whether you are new to FME or a seasoned user exploring advanced capabilities. 

Want to learn more about this feature? Watch our short demo video here.

FME Multi-Language Packs (Beta): Break down language barriers with FME Multi-Language Packs. These AI-powered translation packs are kept in sync with the English version to ensure all FME users have access to the latest features and support, while creating a more inclusive experience for our global community. Four language packs are available now—French, German, Dutch and Hindi—with more planned for future releases.

Want to learn more about this feature? Watch our short demo video here, and learn how to get started here. 

Prefer another language? It’s also available in French, German, Dutch, and Hindi.

DocumentPDF Writer and DocumentPDFStyler: Working together to bring powerful document-generation capabilities to FME Form, enabling users to produce high-quality, professional PDFs directly within their workflows. Unlike FME’s existing PDF formats, which focus primarily on maps and 3D models, the DocumentPDF Writer is purpose-built for creating document-style reports with titles, paragraphs, headings, images, and tables, just like documents from MS Word or Google Docs. 

Complementing this, the DocumentPDFStyler transformer provides a rich interface for customizing the visual formatting of these documents. It offers flexible control over layout elements, including text styling, image placement, table formatting, and more, empowering users to design polished, professional-looking PDFs with precision and ease.

Want to learn more about DocumentPDF Writer? Watch our short demo video here.

Additional Enhancements

FME Form

Redesigned Menus and Updated Terminology in Workbench, Data Inspector, and Quick Translator: Top-level menus across FME Form applications have been simplified, with clearer, more consistent language. This redesign helps users, especially new ones, navigate the interface more intuitively and quickly locate what they need.

Want to learn more about this feature? Watch our short demo video here. 

New Canvas Actions and Quick Add Enhancements: A new Add button is now available directly on the workspace canvas. This lets users easily insert a Source (to bring data in), a Destination (to send data out), or a Transformer, speeding up initial workflow construction. 

Table Parameter Added As New Type in User Parameter Manager: Authors can now add Table Parameters in the User Parameter Manager to collect structured, multi-row input—ideal for defining mappings, rule sets, and other configurations. This input type supports cleaner workspace design and is reusable across Flow Apps, custom transformers, and more.

FME Flow

Automatic HTTPS Configuration for FME Flow: Securing FME Flow with HTTPS is now much simpler. A new guided setup, available in the installer or via a PowerShell script, helps you enable encrypted connections quickly and reliably, reducing the risk of configuration errors and simplifying or automating certificate handling.

Flow REST API V4 Now Fully Supported: REST API V4 is now fully supported in FME Flow, bringing faster response times, greater consistency, and broader functionality. With new endpoints for Streams, Engine Management, and Packages, and improved documentation, API V4 gives developers the tools they need to integrate FME Flow into their automated data workflows with confidence.

Transformers

Reprojector Transformers — Adding Rejected Ports: Reprojector transformers now have rejected ports, so workflows can continue even if some features fail to reproject. This update applies to the Reprojector, CsmapReprojector, EsriReprojector, PROJReprojector, and all *AttributeReprojector variants. Additionally, features without a source coordinate system are now rejected, helping ensure data integrity by preventing misleading coordinate tagging.

GeometryValidator — Format-Specific Validation Presets & Enhanced Spatial Standards: The GeometryValidator transformer now includes preconfigured validation presets for Esri, SQL Server, Oracle, and Snowflake to help catch and and fix geometry issues specific to each format. A new Spatial Standard Compliance rule unifies previous OGC checks, with partial support for ISO standards. The 2D self-intersection check is also more robust, with new configuration options for handling boundary styles.

3DSlicer: 3DSlicer lets users cut through 3D and 2D geometries, including solids and point clouds, along a defined or custom plane. It’s ideal for simulations, sectional analysis, and preparing models for downstream processing.

Want to learn more about this new transformer and how to slice features? Watch our short demo video here.

DatabaseQuerier: The DatabaseQuerier unifies querying across SQL and NoSQL databases, replacing SQLExecutor and SQLCreator and allowing users to execute complex queries in a single, configurable tool. With support for "Run Once" or "Input Driven" modes and future-proof design for new query languages, the DatabaseQuerier simplifies data access to improve FME’s interoperability.

ExcelConditionalFormatter: The ExcelConditionalFormatter transformer lets users apply dynamic conditional formatting to Excel output with ease. Ideal for enhancing data presentation, it allows the creation of customizable rules that can be edited within Excel’s Conditional Formatting Rules Manager and supports complex styling across multiple attributes. 

 

Integrations 

IFC Writer (Beta): Powered by the Open Design Alliance (ODA) libraries, the new IFC Writer aligns FME with the latest IFC standards and supports IFC 4.3, improving BIM compatibility across CAD and GIS environments, including ArcGIS. This helps AEC users transfer detailed model data into operational geospatial workflows with greater fidelity. 

New Reader — Microsoft Word .doc/.docx: FME Form now supports reading Word documents in addition to writing them. This unlocks workflows like mail merges and Word-to-PDF conversions, with support for token replacement and content extraction in document order. The new reader will be available in FME 2024.2 and above.

ArcGISAttachmentConnector: ArcGISAttachmentConnector allows full management of attachments in ArcGIS Feature Services—uploading, downloading, updating, and deleting files. It includes metadata access, error handling, and support for both ArcGIS Online and Enterprise services, making it easier to build and manage rich, data-driven applications in Esri environments.

Updated Integrations with ArcGIS: Support for Esri’s latest data types (e.g., datetime with offset, 64-bit integers, true curves) brings FME up to speed with ArcGIS Pro 3.2 and Enterprise 11.2/11.3, keeping Data Interop workflows current and capable. A new ArcGISBranchVersionManager transformer also allows users to manage branch versioning in ArcGIS Enterprise, enabling listing, reconciling, and posting changes to versioned feature services.

Further Simplified Database Integrations — Unified Format for Spatial and Non-Spatial Data: Safe Software has continued the consolidation of major database formats in FME to support both spatial and non-spatial tables under one unified format name. 

Improved formats:

  • Microsoft SQL Server
  • Microsoft Azure SQL Database
  • Oracle
  • Oracle Autonomous

Stay tuned for further database unification in future releases.

Want to learn more about this feature and spatial data simplification? Watch our short demo video here.

 

Jeej! Exited!

Great work team!

This is amazing!! Thank you Safer! 🐼

​@viviantang since upgrading to 2025.1 (Build 25606), I’m receiving an error message when trying to write data to a new non-spatial table using the MSSQL writer. Are there any known issues with this? Do I need to set a certain parameter on the writer?

 

Microsoft SQL Server Writer: The default spatial column name and type were not specified

Yes. This is a big leap. Thanks for the highlights. Cannot wait to get our system up to 2025.1!

​@viviantang since upgrading to 2025.1 (Build 25606), I’m receiving an error message when trying to write data to a new non-spatial table using the MSSQL writer. Are there any known issues with this? Do I need to set a certain parameter on the writer?

 

Microsoft SQL Server Writer: The default spatial column name and type were not specified

Hi ​@dannymatranga,

In 2025.1 The Microsoft SQL Server Spatial and Non-Spatial readers and writers were merged into a singular Microsoft SQL Server reader and writer. If you have not already, please upgrade your transformer and try again. If you already have upgraded the transformer or if upgrading does not resolve your issue, please create a Support ticket.

Has anyone seen the DatabaseQuerier Transformer? 🤓

=> Here it is ;). Most likely due to low initial relevance it is only shown in quick add after entering the “q” :
 

 

Damn 😏

Damn 😏

Oh damn, did I just get myself blocked?

Damn 😏

Oh damn, did I just get myself blocked?

haha banned!

Does your network permit any AI? In my company blocking every AI other than Copilot, I’m pretty sure I won’t be able to use it :(

Really nice to see the updates for PDF writing… TBH, I’m a little more excited about this that the AI features? Ha, people still love getting PDF reports…. 😂

Hats off Safers! Probably the best release in last years!

Has anyone seen the DatabaseQuerier Transformer? 🤓

=> Here it is ;). Most likely due to low initial relevance it is only shown in quick add after entering the “q” :
 

 

​@tino - If you change the quick add settings to ‘Sort Alphabetically’ then it shows up pretty quick :)

 

 

I don't feel like there are many practical functions. When will FME improve its 3D related converters? It's too difficult to use. Has the 3dtiles format been improved?

​@virtualcitymatt Sorry you’re having AI problems. There shouldn’t be anything in place to ban you, but we’re not getting good feedback from the AI about this sort of error. We’re looking into it, plus ways to improve how we analyze large workspaces. The developers already have some good ideas, though I don’t know when they might get implemented.

​@virtualcitymatt Sorry you’re having AI problems. There shouldn’t be anything in place to ban you, but we’re not getting good feedback from the AI about this sort of error. We’re looking into it, plus ways to improve how we analyze large workspaces. The developers already have some good ideas, though I don’t know when they might get implemented.

Thanks ​@mark2atsafe - I was just stress testing it 😅. 

I don't feel like there are many practical functions. When will FME improve its 3D related converters? It's too difficult to use. Has the 3dtiles format been improved?

Thanks for your feedback ​@charry ! We’re always looking to improve FME’s 3D capabilities, so I’d really like to understand what you’re finding difficult or missing with regards to 3D related convertors. 

I know you’ve previously mentioned adding support for Cesium 3D tiles v1.1 — it’s on our roadmap, but development hasn’t started yet, so I can’t confirm which version it will be in. If you have examples or pain points to share, they’d be incredibly helpful in shaping our priorities.

 

Feel free to comment here or reach out to me directly at andrea.eisma@safe.com — I’d love to hear more.

Hi,

Since upgrading to FME 2025.1 Build 25615 a bug has appeared: when I change table handing in PostGIS writer’s parameters (e.g Create if needed to Truncate existing) and then I apply table handing modifications to all the writers in Workbench, the geometry type is also changed for all of them. This is really annoying when we have to check all geometries in workbenchs with a lot of readers. 

An exemple: three writers with three different geometries (polygon, line, point). After apply changes, all of them have polygon geometries 

 

 

Hi ​@pabloolivaresm ,

Thanks for reporting this. I’ve reproduced this issue and have filed a ticket for our development team to look into (internal report: FMEFORM-34665).

If you encounter any other issues, please submit a ticket to our support team to further assist.

Thank you!

Andrea

Community Stats

31,838
Posts
120,908
Replies
39,468
Members

Latest FME

Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.