Appearance
Choose a static visual when the insight is fixed, the output is print or an archive, and you have one clear message; choose interactive when users genuinely need to explore a large or multidimensional dataset themselves. For most historians and archivists the static option is the safer default — it is durable, citable and accessible by default — while interactivity is a deliberate investment justified only by real exploratory need. Here is how to decide and how to build either well.
What is the real difference for a historian?
A static visual is a fixed image — a PNG, SVG or chart in a PDF. It says one thing, the same way, forever. An interactive visual runs in a browser and lets the reader act on it: zoom a map, filter a timeline, hover for detail, search a network. The difference is not aesthetic but archival and rhetorical: static visuals make an argument, interactive visuals offer a tool. A monograph figure showing mortality across a famine is static by nature; a portal letting researchers explore 200 years of parish registers is interactive by necessity.
When should you choose static?
Default to static when any of these hold:
- The output is print, a PDF, or a journal that will not run JavaScript.
- The work must survive for decades — static images do not bit-rot.
- You have a single, well-defined message.
- Accessibility and citation matter and resources are limited.
Static wins on durability. A figure.svg committed to a repository will render identically in twenty years; an interactive D3 page may not survive two major library versions. For the scholarly record, that durability is often decisive.
When does interactivity actually earn its cost?
Interactivity is justified when exploration adds genuine insight that no single fixed view can deliver:
- The dataset is too large for one frame (tens of thousands of records).
- Users have different questions — one wants Norfolk, another wants 1851.
- The data is multidimensional and filtering reveals structure.
- The audience is exploratory: researchers, students, a public portal.
If your finding fits in one image, interactivity is decoration. If readers need to ask their own questions of the data, it is the point.
How do the trade-offs compare side by side?
| Dimension | Static | Interactive |
|---|---|---|
| Build cost | Low | High |
| Maintenance | Near zero | Ongoing (library updates) |
| Preservation | Excellent | Poor without fallback |
| Accessibility | Alt text + contrast | + keyboard, screen reader, focus |
| Citation | Stable, archivable | Needs snapshot for citation |
| Best for | One message, print, archive | Exploration, large data, portals |
| Tools | ggplot2, matplotlib, Datawrapper export | D3, Observable, Plotly, Leaflet |
The maintenance row is the one historians underweight. An interactive piece is software, and software needs upkeep; a static image is a document, and documents sit quietly.
How do you build either in a sensible workflow?
The robust pattern is static-first, interactive-as-enhancement. Build the canonical static figure, then layer optional interaction for the web while keeping the static version as the citable record.
python
# Static-first: one matplotlib figure, exported as the archival artefact
import matplotlib.pyplot as plt
fig, ax = plt.subplots()
ax.plot(df["year"], df["burials"])
fig.savefig("burials.svg") # durable, citable, accessible with alt textFor the web layer, a tool like Datawrapper lets you publish an interactive chart and download a static fallback PNG from the same source — a pragmatic middle path that needs little code. For heavier interactivity, Observable or Plotly produce embeddable widgets, but always export a static snapshot to archive alongside.
What about accessibility and preservation?
These two concerns push hard toward static. A static image needs only descriptive alt text and adequate colour contrast to be accessible. An interactive visual additionally demands keyboard navigation, ARIA roles, screen-reader announcements and focus management — substantial work that is frequently skipped, leaving the visual unusable for many readers. For preservation, always archive a static fallback image plus the underlying data file, so the insight survives even when the JavaScript does not. Treat the interactive version as the perishable layer and the static version as the permanent one.
Key Takeaways
- Default to static: it is durable, citable and accessible with minimal effort.
- Choose interactive only when users genuinely need to explore large or multidimensional data.
- Interactive visuals are software — they carry ongoing maintenance and bit-rot risk.
- Build static-first, then add interactivity as an enhancement, not the foundation.
- Always archive a static fallback and the raw data alongside any interactive piece.
- Accessibility is far cheaper for static (alt text, contrast) than interactive (keyboard, ARIA).
- Datawrapper offers a pragmatic middle path: interactive web plus static export.
Frequently Asked Questions
When is a static visual the better choice?
Choose static when the insight is fixed, the medium is print or PDF, the work must be archived long-term, or you have one clear message to deliver. Static images are durable, citable and accessible by default.
When does interactivity genuinely add value?
Interactivity pays off when users need to explore — filter by date, search for a place, drill into detail — and when the dataset is too large or multidimensional to fit one fixed view. Exploration, not decoration, justifies it.
Are interactive visuals harder to preserve?
Yes. Interactive visuals depend on JavaScript libraries that age and break, so they suffer "bit rot" over years. Always archive a static fallback image and the underlying data alongside any interactive piece.
What about accessibility?
Static images need only good alt text and sufficient colour contrast. Interactive visuals additionally require keyboard navigation, screen-reader support and focus management, which is substantial extra work often skipped.
Can I get the benefits of both?
Yes — design the static version first as the canonical, archivable artefact, then layer optional interactivity on top for the web. The static view remains the citable record; interaction is an enhancement, not the foundation.