What Is Web-Based Art? Understanding Browser-Based and Net Art Practices

Web-based art is artwork made for, in, or about the web browser. Instead of treating the browser as a neutral frame for displaying a painting or video, the artist treats it as the medium itself: its code, links, loading behavior, screen dimensions, and interactivity become the material. If you can open a work at a URL, navigate it with a mouse or keyboard, and it changes or responds as you do, you are likely looking at web-based art.

That definition sounds simple, but it sits inside a cluster of overlapping terms—net art, digital art, browser-based art, internet art, post-internet art—that are often used interchangeably and shouldn't be. This guide sorts out the distinctions, explains how artists actually work with the browser, and gives you practical ways to view and discuss the work.

The core distinction: medium vs. channel

The fastest way to understand web-based art is to ask whether the web is a channel or a medium.

• Channel: The web is just delivery. A gallery uploads documentation photos of a sculpture, or a filmmaker streams a video. The artwork would exist the same way in a physical room.
• Medium: The web is the substance. The work depends on the browser to exist at all. Remove the URL, the code, or the network, and there is no artwork left.

Web-based art belongs to the second category. This is why a JPEG of a painting on an artist's site is not web-based art, but a page that assembles itself from fragments each time you reload it probably is.

Web-based art vs. net art vs. digital art

These terms are related but not identical. The table below is a working guide, not a rigid taxonomy—artists and historians disagree at the edges.

A useful rule of thumb: net art is often about the internet as a cultural condition; web-based art is often about the web as a technical and aesthetic material. Many works are both.

The browser as an artistic medium

When artists treat the browser as a medium, they gain a specific set of properties to work with. These are the recurring techniques you'll encounter.

Code as material

Artists write HTML, CSS, JavaScript, and increasingly WebGL or shader code. The code isn't hidden plumbing—it's often the point. A work might be a single page of readable source, or a script that generates a different composition on every visit. Because the source is usually viewable in the browser, the "backstage" becomes part of the artwork.

Animation and motion

The browser is a natural home for animation: looping GIFs, canvas animations, CSS transitions, and video embedded directly in a page. This is where web-based art overlaps with experimental video—both often reject narrative and linear time in favor of rhythm, repetition, and abstraction.

Interactivity and response

The browser knows where your cursor is, how fast you scroll, how large your window is, and what you click. Artists use these signals as inputs. A work might respond to mouse movement, refuse to load until you interact, or rearrange itself based on your screen size. Interactivity here is not a game mechanic; it's a way of making the viewer's presence part of the composition.

Links, networks, and instability

Hyperlinks let a work point outside itself—to other sites, to dead URLs, to live data. This makes web-based art inherently unstable. Links rot, plugins deprecate, servers go offline. Some artists treat that fragility as content, building works that are meant to decay or that document their own disappearance.

Abstraction and non-representation

Not all web-based art depicts anything. A great deal of it is abstract: color fields generated by algorithms, geometric animation, typographic experiments, glitch and compression artifacts. This connects it to the longer history of abstract painting and drawing, even when no paint is involved.

How to view and interpret web-based art

Approaching this work is different from standing in front of a canvas. Here's a practical sequence.

1. Open it in a real browser, not a screenshot. The work's behavior is the work. A still image tells you almost nothing.
2. Note the entry point. Does it load instantly or slowly? Does it ask you to click, wait, or scroll? The first ten seconds are usually deliberate.
3. Interact deliberately. Move the cursor, resize the window, reload the page, try the keyboard. Many works reveal themselves only through use.
4. Check the source if it's available. Viewing the page source is not cheating; for many artists it's an invited part of the experience.
5. Ask what the browser is doing. Is it framing, hiding, generating, or breaking something? The answer usually points to the work's idea.
6. Consider context. Was it made for a gallery screen, a festival, a personal site, or a commission? Context shapes how the work expects to be seen.
7. Accept that it may not work. Broken works are common. Sometimes that's a technical failure; sometimes it's the piece.

Questions worth asking in front of a work

• What would be lost if this were printed or shown as a video?
• Does the work depend on my input, or would it run the same without me?
• Is the code, the network, or the screen the real subject?
• How does it handle time—loop, one-shot, or endless?
• What happens when I leave the page?

Where web-based art sits in contemporary art

Web-based art has moved from a niche subculture into mainstream contemporary art contexts. You'll now find it in:

• Online exhibitions and digital commissions hosted by museums and arts organizations
• Artist portfolios and studio sites, where the site itself may be a work
• Festivals and biennials dedicated to digital or media art
• Gallery presentations, often on dedicated screens or projections
• Archives and preservation projects, since the work tends to disappear

This is also where the vocabulary gets practical. When you browse a contemporary art site—especially one showing San Francisco contemporary art, experimental video, abstract animations, paintings, drawings, and installations—you may see web-based work presented alongside physical media. The categories aren't in competition; they're different answers to the same questions about space, time, and perception.

A short glossary for online exhibitions

• Browser-based: The work runs in a browser and depends on it.
• Net art: Art using the internet as context, often with a critical or cultural angle.
• Generative: The work produces itself from rules or randomness; each viewing may differ.
• Interactive: The work responds to viewer input.
• Real-time: The work changes continuously rather than playing back a fixed file.
• WebGL / shader: Technologies for 3D and GPU-driven graphics in the browser.
• Preservation / emulation: Efforts to keep fragile works viewable after their original tech becomes obsolete.
• Documentation: Stills or video of a work, useful but never a substitute for the live piece.

Practical takeaways

If you're new to web-based art, start with one work and spend ten minutes with it. Interact, reload, resize, and read the source. Then ask whether the web is a channel or a medium in what you're seeing—that single question will orient you faster than any definition.

If you're an artist, the same question applies to your own practice. Deciding whether the browser is your delivery system or your material will shape everything: how you build, how you show, and how your work survives.

And if you're just browsing, remember that web-based art is one of the few art forms you can experience exactly as intended, right now, on the same device you're reading this on. That accessibility is not a compromise. It's the point.