GIS Portfolio Platforms - Compared Features, Usability, and Pricing

I asked the AI agent of Wix to generate a blog post on a topic that might interest fellow GIS practitioners. Funny enough, ArcGIS Instant App, which hosts my public AGOL portfolio, is absent from this list. In my opinion, Instant App is more suitable for an ArcGIS portfolio than Story Maps. Nevertheless, I hope you will find this post as informative and inspiring as I did. I will definitely give Mapbox a try...

"A GIS portfolio has one job: prove that you can turn spatial data into clear, useful work. A static resume can list QGIS, ArcGIS Pro, Python, PostGIS, or remote sensing. A good portfolio shows the analysis, the map, the choices behind it, and the story a reviewer can understand in two minutes.

The tricky part is choosing where to build it. Some platforms make beautiful narrative maps with little setup. Others give you full control but expect coding skills. A few are excellent for dashboards or public data apps, yet awkward for explaining your process.

This guide compares the best GIS portfolio platforms available, with a focus on features, usability, and pricing. It also includes real-world-style case studies based on common portfolio scenarios.

What makes a strong GIS portfolio platform

The best platform is not always the most advanced one. It is the one that helps the right audience understand your work.

A hiring manager may want polished case studies and clean visuals. A GIS lead may look for data sources, methods, accuracy limits, and technical depth. A client may care most about whether the map loads quickly and answers a practical question.

A strong GIS portfolio platform should help with at least four things:

• Publishing maps

  Web maps, dashboards, story maps, or embedded interactive maps should be easy to share.

  
  

• Explaining methods

  A portfolio should show how you handled data cleaning, projections, analysis, cartography, and uncertainty.

  
  

• Presenting finished work

  The platform should make your work look credible without distracting templates or clutter.

  
  

• Supporting growth

  You should be able to add new projects, update old ones, and link to code, data, or documentation.

  
  

Pricing also matters. A student building a first portfolio has different needs than a consultant pitching municipal clients. Free can be perfect, but only if the platform does not limit the kind of work you need to show.

Quick comparison of popular GIS portfolio platforms

Prices change often, so treat this as a planning guide rather than a quote. Always check each provider’s current pricing page before committing.

Platform	Best for	Usability	Pricing pattern	Main limitation
ArcGIS StoryMaps and ArcGIS Online	Polished GIS stories, public-sector portfolios, Esri-heavy roles	Easy to moderate	Paid ArcGIS account, with education and personal-use options in some cases	Best features sit inside the Esri ecosystem
Felt	Fast, attractive web maps and lightweight collaboration	Easy	Free tier plus paid plans	Less suited for complex analysis documentation
GitHub Pages with Leaflet or MapLibre	Technical portfolios, open-source work, code samples	Moderate to advanced	Free hosting for public repositories	Requires comfort with HTML, JavaScript, and Git
Mapbox	Custom interactive maps and developer-focused portfolios	Advanced	Free tier with usage-based paid pricing	Costs and setup can grow with traffic and complexity
CARTO	Spatial analytics, dashboards, business location intelligence	Moderate to advanced	Paid plans, often aimed at teams	May be more platform than a solo portfolio needs
QGIS Cloud	Publishing QGIS projects with minimal web setup	Moderate	Free or paid tiers depending on needs	Design flexibility is limited compared with custom sites
Tableau Public	Dashboard-style spatial data presentations	Easy to moderate	Free public publishing	Maps are not as GIS-native as dedicated mapping tools
WordPress, Wix, or Squarespace with embedded maps	A polished personal website with GIS examples	Easy	Free trials or paid website plans	The map experience depends on embedded tools

ArcGIS StoryMaps is the strongest polished portfolio choice for Esri-focused work

ArcGIS StoryMaps is often the safest choice for GIS students, analysts, and public-sector professionals who want a polished portfolio without building a website from scratch. It combines text, maps, images, sidecar panels, and embedded content in a format that feels natural for case studies.

Its biggest strength is communication. You can walk through a flood-risk analysis, a transit access study, or a habitat suitability model with maps placed exactly where the explanation needs them. If your target roles mention ArcGIS Pro, ArcGIS Online, Survey123, Dashboards, or Experience Builder, StoryMaps also signals that you know the Esri workflow.

Usability is one of its best traits. The editor is clean, and most people can produce a presentable story quickly. The learning curve appears when you connect multiple hosted layers, configure sharing permissions, or maintain web maps across several projects.

Pricing depends on your ArcGIS access. Students may have access through a university. Some individuals use ArcGIS for Personal Use for noncommercial work. Professional or commercial use usually requires an ArcGIS Online subscription or named user license.

Case study

A recent urban planning graduate could use StoryMaps to present a walkability analysis. The story might include census data, sidewalk coverage, bus stops, and a final suitability map. The strength is clarity. A reviewer can follow the question, methods, and result without downloading anything.

The weakness is portability. If the graduate later loses school access, hosted layers and stories may need to move to another account. For that reason, keep local copies of datasets, screenshots, project notes, and exportable maps.

Best fit:

• Public-sector GIS roles

• Environmental planning

• Urban planning

• Emergency management

• GIS analyst portfolios where storytelling matters

  
  

Felt is excellent for fast, modern web maps

Felt has become popular because it makes web mapping feel quick and visual. You can upload data, style layers, add notes, and share a map without spending hours on setup. For a portfolio, that speed is valuable.

Felt works especially well when the map itself is the main artifact. A bike infrastructure map, neighborhood tree inventory, zoning comparison, or community asset map can look clean with limited effort. Collaboration features also help if a class project or volunteer project involved multiple contributors.

The interface feels more like a modern design tool than a traditional GIS platform. That makes it approachable, but it also means it may not show the full technical process behind your analysis. If the job you want values data engineering, scripting, model building, or enterprise GIS administration, Felt should be paired with a written case study or a GitHub link.

Pricing usually includes a free tier and paid plans with more capacity or team features. The free option can be enough for public portfolio pieces, but check limits around private maps, data size, exports, and collaboration.

Case study

A community volunteer group mapping cooling centers during a heat event could use Felt to publish a clear, public-facing map quickly. The strength is speed. The group does not need a full GIS server or developer support.

The weakness is depth. If the portfolio owner wants to explain geocoding quality, service-area modeling, or demographic joins, that explanation needs to live outside the map or in linked notes.

Best fit:

• Quick public maps

• Community mapping projects

• Visual portfolios

• Early-career GIS professionals who want something clean fast

  
  

GitHub Pages is the best choice for technical prowess.

GitHub Pages is not a GIS platform in the traditional sense. That is part of its appeal. It lets you publish a free static website from a GitHub repository, then build interactive maps with libraries such as Leaflet, MapLibre GL JS, OpenLayers, or deck.gl.

For technical GIS roles, this can be the strongest portfolio option. It shows that you can work with code, version control, web maps, GeoJSON, APIs, and documentation. You can also include notebooks, scripts, data processing steps, and README files.

The downside is setup. A simple GitHub Pages site is not hard, but a good one takes time and effort. You need to think about responsive design, file size, data hosting, accessibility, browser performance, and broken links. Large spatial datasets can become awkward unless you simplify geometries, tile data, or use external services.

Pricing is a major advantage. Public GitHub repositories and GitHub Pages hosting are free for many common portfolio uses. Costs may appear if you need private repositories, paid data hosting, custom domains, or external APIs.

Case study

A GIS analyst transitioning into geospatial development could build a portfolio with three projects: a Leaflet parcel viewer, a MapLibre vector tile map, and a Python notebook that cleans crash data. Each project can include code, screenshots, and plain-English notes.

The strength is proof. Reviewers can inspect the work. The weakness is polish. A technically strong GitHub portfolio can still feel rough if the homepage, navigation, or writing is neglected.

Best fit:

• Geospatial developer roles

• Python, JavaScript, or PostGIS portfolios

• Open-source GIS work

• Applicants who want to show code and process

  
  

Mapbox is powerful when custom design matters

Mapbox is a strong choice when you want highly customized interactive maps. It supports polished basemaps, vector tiles, custom styling, routing, geocoding, and developer tools. A portfolio built with Mapbox can feel smooth and professional when done well.

It works best for people who already have web development skills or want to build them. You can create a custom project site. Use Mapbox GL JS, style data in Mapbox Studio, and build interactions that would be hard in a template-based platform.

The main tradeoff is complexity. Mapbox gives you control, but it also asks you to understand tokens, usage limits, web development, and API pricing. For a small public portfolio, the free tier may be enough. If a project gets heavy traffic or uses paid services, costs can rise based on usage.

Case study

A transportation analyst could build a custom map showing transit frequency by time of day, with animated stops and route filters. Mapbox would make the interaction feel polished. The project could stand out for roles that value user-facing map applications.

The weakness is maintenance. If code libraries change, access tokens are exposed, or usage rules shift, the portfolio owner has to manage it.

Best fit:

• Custom web map applications

• Developer portfolios

• Cartographic design-heavy projects

• Interactive transportation, real estate, or mobility maps

  
  

Technical GIS portfolios often benefit from showing how data was collected and checked.

CARTO is best for spatial analytics portfolios

CARTO focuses on cloud-native spatial analysis, data visualization, and location intelligence. It is a strong platform for portfolios that need to show more than a pretty map. If your work involves large datasets, business locations, mobility data, demographics, or spatial SQL, CARTO can make a strong impression.

Its visual tools are approachable, but the platform becomes most useful when paired with cloud data warehouses and analytical workflows. That makes it feel more advanced than beginner-friendly tools.

Pricing is usually aimed at professional users and teams, so it may be too much for a student portfolio unless you have access through an organization, trial, or program. For someone targeting location intelligence or analytics roles, the cost and learning curve may be justified.

Case study

A retail site-selection portfolio could use CARTO to compare trade areas, competitor locations, drive-time zones, and demographic patterns. The strength is analytical credibility. The weakness is that a reviewer outside analytics may not need that much complexity.

Best fit:

• Location intelligence

• Spatial SQL portfolios

• Business GIS

• Cloud data workflows

• Analytics-heavy case studies

  
  

QGIS Cloud is practical for QGIS users who want web publishing

QGIS remains one of the most important open-source desktop GIS tools. QGIS Cloud gives users a way to publish QGIS projects to the web without building a custom hosting stack.

The appeal is simple: build the project in QGIS, then publish it. For people who already work in QGIS, that workflow feels natural. It can be a good way to show open-source GIS skills, especially when combined with project write-ups on a personal site.

The limits are mostly design and flexibility. A QGIS Cloud map may not feel as polished as a StoryMap or as custom as a Mapbox app. It is better as a map publishing tool than as a full portfolio website.

Pricing usually includes a limited free option and paid plans for more serious use. Check storage, service limits, custom branding, and public access rules before relying on it.

Case study

An environmental consultant could publish a wetland assessment map from QGIS, then link to a PDF methods summary and data dictionary. The strength is speed for QGIS-based work. The weakness is presentation. The portfolio still needs a home page or written case study to frame the map.

Best fit:

• QGIS users

• Open-source GIS portfolios

• Simple public web maps

• Consultants who need to publish project layers quickly

  
  

Tableau Public is useful for spatial dashboards, with limits

Tableau Public is not a full GIS platform, but it deserves a place in the comparison. Many GIS jobs include dashboards, charts, and spatial summaries. Tableau can present those clearly, especially when the map is one part of a broader data story.

It is easy to share, visually clean, and free for public work. That makes it useful for portfolios involving public datasets, such as housing trends, crash locations, service coverage, or environmental indicators.

The main limitation is GIS depth. Tableau maps work well for many thematic and point-based use cases, but they are not a replacement for GIS analysis tools. If your portfolio depends on projections, topology, raster analysis, network analysis, or advanced cartography, use Tableau as a presentation layer rather than the main proof.

Case study

A public health analyst could build a dashboard showing clinic access by county, with maps, filters, and trend charts. The result may be easier for a non-GIS audience to understand than a traditional web map. The weakness is that the GIS methods need to be explained elsewhere.

Best fit:

• Data analyst roles with spatial work

• Public dashboards

• Chart-heavy GIS stories

• Portfolios aimed at mixed technical and nontechnical audiences

  
  

Website builders work well as the front door

WordPress, Wix, Squarespace, and similar tools are not GIS platforms, yet they can be excellent portfolio homes. They give you an About page, project pages, resume links, contact forms, and clean navigation. Then you can embed StoryMaps, Felt maps, Tableau dashboards, GitHub projects, or Mapbox apps.

This is often the most practical setup. Use a website builder as the front door, then choose the right mapping tool for each project.

Pricing varies by provider, but expect free trials or basic paid website plans. A custom domain usually costs extra. The main weakness is that embedded maps can feel inconsistent if each project comes from a different platform.

Case study

A mid-career GIS analyst could create a simple website with five project pages: one StoryMap, one Felt map, one GitHub project, one dashboard, and one PDF cartography sample. This gives reviewers a clean path through varied work without forcing every project into one tool.

Best fit:

• General GIS portfolios

• Consultants

• Career changers

• Anyone with work spread across several platforms

  
  

The best platform depends on the type of GIS work you want to show.

How to choose the right GIS portfolio platform

Start with the role or client you want, then choose the platform that supports that goal.

If you want a public-sector GIS analyst role, ArcGIS StoryMaps plus ArcGIS Online is hard to beat. It matches common government workflows and helps you explain project context clearly.

If you want a geospatial developer role, GitHub Pages with Leaflet, MapLibre, or another web mapping library gives stronger proof of skill. Add clear documentation so the code does not have to speak alone.

If you need a fast visual map, Felt is a smart choice. It is especially useful for community projects, class projects, and maps that need to be shared quickly.

If your work depends on custom interaction and polished map design, Mapbox may be worth the learning curve.

If your portfolio is about spatial analytics, CARTO can show higher-level data work. If your background is QGIS, QGIS Cloud can help publish familiar projects. If dashboards matter, Tableau Public can round out the story.

For many people, the best answer is a combination:

• A personal website as the home base

• StoryMaps or Felt for narrative and visual projects

• GitHub for code and reproducible analysis

• Tableau or CARTO for dashboard and analytics work

• PDF map samples for cartographic polish

  
  

A portfolio does not need ten projects. Three strong, well-explained projects usually beat eight shallow examples. Each one should answer a simple question: what problem did this solve, what data did you use, what did you do, and what would you improve next time?

Final recommendation

The best all-around platform for a polished GIS portfolio is ArcGIS StoryMaps, especially for students, analysts, planners, and public-sector applicants. The best technical option is GitHub Pages, because it proves coding and web mapping ability. The best quick visual mapper is Felt, while Mapbox stands out for custom interactive applications.

Choose based on your goals, not on popularity. A portfolio for environmental planning should not look the same as one for geospatial software development. Pick the platform that lets your strongest work make sense fast, then write enough context to show the thinking behind the map."