- Can I migrate stories made from the classic Esri Story Maps templates into ArcGIS StoryMaps?
- What is the plan for stories authored with the classic Esri Story Maps templates?
- Will the classic Esri Story Maps continue to be maintained and updated?
- What media file types and sizes are supported in ArcGIS StoryMaps?
- Does ArcGIS StoryMaps work in a disconnected environment?
- Does ArcGIS StoryMaps follow WCAG 2.0 guidelines for accessibility?
- Does ArcGIS StoryMaps consume credits?
- How does premium content work in ArcGIS StoryMaps?
- How do I find and add public maps from ArcGIS Online?
- How can I track audience metrics for my stories?
- Does the ArcGIS Developer dashboard support ArcGIS StoryMaps?
- Can I create a PDF file of a story?
- Can I create a copy of a story?
- What does beta mean?
No. The story builder in ArcGIS StoryMaps is not a new template or an update to the classic Story Maps templates. Instead of templates, ArcGIS StoryMaps uses a dynamic story builder with modern capabilities. When authors create and publish a story, they typically spend time getting that particular visual treatment approved and they socialize the story at a specific URL. For these and other reasons, ArcGIS StoryMaps does not include the option to update stories built with the classic Story Maps templates, and there is no migration tool to bring stories created with the classic templates into ArcGIS StoryMaps. For more information about the differences between the classic Esri Story Maps and ArcGIS StoryMaps, see What is ArcGIS StoryMaps.
Stories created with the classic Esri Story Maps templates will continue to be available to authors and readers. As Esri moves forward with ArcGIS StoryMaps, authors can still create and edit stories with the classic templates, and these stories will continue to be available to their audiences. ArcGIS StoryMaps is the next-generation storytelling tool in ArcGIS, and story authors are encouraged to use this new tool to create stories. For more information about ArcGIS StoryMaps, see the Product road map page.
For images, the story builder supports image file sizes up to 20 MB for the following file types: JPEG, JPG, JFIF, PNG, SVG, GIF, and BMP. For video uploads, the story builder supports MP4 files up to 50 MB. When an MP4 video is uploaded for background use on a cover or in an immersive media panel, the video automatically plays and its audio is not available. For audio uploads, the story builder supports audio files up to 50 MB for the following file types: MP3 and WAV.
Yes. ArcGIS StoryMaps is available in ArcGIS Enterprise starting at version 10.8.1. For more information, see System requirements.
Yes. In accordance with WCAG 2.0 guidelines, ArcGIS StoryMaps supports HTML tags, semantic structure, color contrast, keyboard navigation, alternative (alt) text, and other design and feature considerations in the story builder. This allows authors to create stories that are accessible to a broad audience as they take advantage of these capabilities. For more information about accessibility, see Accessibility and supported languages.
Credits are the currency used in ArcGIS Online and across ArcGIS for transactions such as storage, spatial analysis, and using premium content. Authoring stories in the ArcGIS StoryMaps builder does not consume credits. When using ArcGIS StoryMaps in ArcGIS Online, credits are consumed for data storage (uploaded images and video), capabilities that use premium content (ArcGIS Living Atlas maps), and ArcGIS Online analysis. If you create a map that uses hosted feature service layers, tile service layers, or both, credits may be consumed for data storage. To learn more about credits and how they are used, see Understand credits and ArcGIS Online Credits Overview. ArcGIS StoryMaps does not consume credits in ArcGIS Enterprise unless premium ArcGIS Living Atlas content has been added to a story. For more information about premium content, see Configure Living Atlas content.
To manage credits, you can periodically review your published stories and unpublish any that are no longer needed or being used. You can also delete any layers that are no longer needed and archive data offline.
If your story includes maps or scenes that consume premium services or data, they will consume credits based on the number of times the story is viewed. If you are concerned about this, speak with your ArcGIS organization administrator to limit those credits, or see Credits.
First find the web map or web scene on ArcGIS Online and add it to your favorites list. Then you can add that map or scene to your story from the My Favorites tab in the story builder's map browser. For more information, see Add maps. If your ArcGIS Enterprise environment does not have access to the internet, these public maps from ArcGIS Online are not available.
You can get detailed audience metrics for a story by adding a Google Analytics tracking ID in the story settings. Google Analytics can provide information about page views, audience demographics and language preferences, and engagement with story buttons, links, and maps. For more information, see Add analytics to a story.
The view count for the ArcGIS item details does not reflect the number of people who have viewed your published story.
Yes, the ArcGIS Developer app dashboard supports the StoryMap itemType. You can use this dashboard to limit the application proxies or change the referrers that are allowed; the REST API is not required for these tasks. Additionally, the ArcGIS Developer site supports app proxies for the classic Esri Story Maps.
Yes, ArcGIS StoryMaps supports creating PDF files from stories through the print dialog. For more information, see Print a story.
Yes, you can create a copy of a story that you own on the Stories page by selecting the Duplicate option from the story card's quick actions menu or by selecting Duplicate story in the story builder's More actions menu. The duplicate option in the story builder is available for administrators and members of any shared update groups to which the story is shared. This option can be used to create a copy of a story or to use an existing story as a template for a new story. Collections and themes can be duplicated as well. For more information about creating groups with shared update capabilities, see Coauthor a story or a collection.
Beta components and features may have incomplete functionality or documentation, may undergo minor unannounced changes, and are subject to change without notice. Beta components and features are usually available in English only. If you have issues or are experiencing problems with any of the beta functionality, contact Esri Technical Support or visit the Esri Community page.
No. The ArcGIS StoryMaps team may enable more customization options in the future, but ArcGIS StoryMaps does not support custom HTML or CSS at this time. If you have a specific request for customization or the types of HTML or CSS you want to add, contact the team.
Yes. The ArcGIS StoryMaps builder automatically saves your work as you go. This includes additions, deletions, and changes to a story's content, configuration, and settings. Since this is always working in the background, it's recommended that you do not have the story builder open in multiple browser tabs—or on multiple devices—simultaneously editing the same story. This can result in lost work or other inconsistencies. Changes made outside the current browser tab are not reflected in your current builder session until you reload the builder.
Authors can link to web content through buttons and hyperlinked text. ArcGIS StoryMaps supports the following link protocols: https, mailto, iform, tel, flow, lfmobile, arcgis-navigator, arcgis-appstudio-player, arcgis-survey123, arcgis-collector, arcgis-workforce, arcgis-explorer, arcgis-trek2there, mspbi, comgooglemaps, pdfefile, pdfehttp, pdfehttps, boxapp, boxemm, awb, awbs, gropen, and radarscope.
No. ArcGIS StoryMaps does not support exporting features or data from express maps. Express maps are designed to be simple maps rather than structured data sources. For more information about express maps, see Add maps.