jtwine.com No paid content found

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.

Net art is art made specifically for the internet and meant to be experienced through a network connection, usually in a browser. It is not simply a photograph of a painting posted online, and it is not a digital file that happens to live on a website. The network itself—its links, its loading times, its screens, its ability to connect distant people—is part of the material the artist works with. If you can download a net art piece, print it, and hang it on a wall without losing what makes it art, it probably was not net art to begin with.

Net art vs. digital art vs. internet art

These terms get used loosely, so it helps to separate them.

The practical test is dependence. A digital video can be shown in a gallery. A net art piece that asks you to click through a shifting set of pages, or that changes based on what other visitors are doing, loses its meaning when you pull it off the network.

Where net art came from

Net art emerged in the late 1980s and grew through the 1990s, when dial-up connections, early browsers, and cheap personal websites made the internet feel like a new frontier. Artists noticed that the web was not neutral: it had its own aesthetics, its own politics, and its own ways of controlling attention. Early net art often looked deliberately rough—raw HTML, animated GIFs, broken links, scrolling text—because the artists were treating the browser as a studio rather than a storefront.

By the 2000s, net art had moved into museums and biennials, and by the 2010s it had influenced social media art, glitch art, and much of what we now call post-internet art. The term "net art" is sometimes used narrowly for the 1990s wave and sometimes broadly for any network-dependent practice today.

Key characteristics

• Network dependence. The piece needs a connection to function. Remove the network and you remove the art.
• Interactivity. Viewers click, type, scroll, or wait. The artwork responds, so the experience is different for each person.
• Hypertext and linking. Links are not just navigation; they can be the composition. A net art piece may be a chain of pages, a loop, or a web of references.
• Time and change. Pages load, images fail, content updates. Impermanence is often part of the point.
• Distribution as art. Some net art is about how it spreads, who sees it, and how it is copied or remixed.
• Browser as frame. The window, the address bar, the back button, and the cursor become part of the viewing experience.

Common forms you will encounter

Net art is not one style. You will find:

• Abstract animations. Looping, generative, or code-driven motion that plays in the browser.
• Experimental video. Video that is embedded, streamed, or manipulated in ways that depend on the web.
• Interactive installations. Physical spaces wired to the internet, where online data or remote participants affect what happens in the room.
• Hypertext narratives. Stories told through linked pages rather than a linear sequence.
• Software and code art. Works distributed as scripts, apps, or browser experiments.
• Networked performance. Events that happen online, sometimes with audiences participating in real time.

Paintings, drawings, and other physical works can be part of a net art practice, but they are usually documentation, companions, or entry points rather than the net art itself.

How net art is experienced, exhibited, and preserved

You usually experience net art alone, on your own device, at your own pace. That intimacy is part of its character. But it also creates problems for museums and collectors:

• Hardware and software age. Browsers update, plugins disappear, and old code stops running.
• Link rot. Pieces that depend on external sites break when those sites vanish.
• Variable viewing. A piece may look different on a phone, a laptop, or a large monitor.
• Preservation strategies. Institutions sometimes re-create works, emulate old systems, or document them on video. Each choice changes the piece.

When you see net art in a gallery, you are often seeing a re-staging rather than the original experience. That is not necessarily a failure—it is a known condition of the medium.

How to start exploring

You do not need a degree to look at net art. Try these steps:

1. Use a desktop browser when you can. Many older pieces assume a mouse, a keyboard, and a wide screen.
2. Give it time. Some works load slowly on purpose or unfold over several minutes.
3. Follow the links. If a piece invites you to click, click. The path is often the artwork.
4. Note what breaks. A dead link or a missing image can be part of the piece's history.
5. Look for context. Artist statements, exhibition pages, and archives explain what you are seeing.
6. Visit in person when possible. Contemporary art museums and galleries in cities like San Francisco regularly show web-based and experimental media work alongside physical pieces.

If you are in the San Francisco Bay Area, keep an eye on contemporary art spaces that program experimental video, browser-based work, and installations. These venues often pair net art with paintings, drawings, and sculpture, which makes it easier to see how the medium fits into a broader practice.

A simple way to tell if something is net art

Ask three questions:

1. Does it need a network connection to work?
2. Does the browser or the internet shape how you experience it?
3. Would it lose something essential if you saved it as a file and viewed it offline?

If the answers are yes, yes, and yes, you are probably looking at net art. If not, you may be looking at digital art, documentation of a physical work, or something in between—which is fine, as long as you know which one you are seeing.

"Browser based" describes artwork that lives inside a web browser and treats the browser itself as its medium, not just its delivery method. The piece is typically made with HTML, CSS, JavaScript, WebGL, or similar web technologies, and it only fully exists when someone opens it in a browser and interacts with it. This is different from a video file you download, a digital photo you view, or a physical installation you walk through: a browser-based work depends on the browser's rendering engine, its input devices, and its network connection to become what it is.

The browser as medium, not container

Most digital art is stored digitally but experienced in another form. A digital print is a physical object. A video is watched on a screen. A browser-based work, by contrast, uses the browser's own capabilities as its material:

• Code as the artwork. The source files (HTML, scripts, shaders) are the work. Change the code and you change the piece.
• The rendering engine as the "canvas." How Chrome, Firefox, or Safari draws the page affects color, motion, and timing.
• Input as part of the composition. Mouse position, clicks, scroll, keystrokes, touch, and even window size can drive what happens.
• The network as a condition. Some works load assets, pull live data, or change over time, so the piece is never quite the same twice.

This is why a screenshot of a browser-based artwork rarely captures it. The screenshot shows a moment; the work is the behavior.

Browser based vs. web based vs. net art

These terms overlap, but they are not identical. The distinctions are useful when you are reading about, exhibiting, or writing about a piece.

A single work can be all of these at once. A browser-based piece is usually also web based, and it may sit within the net art tradition. The label you choose depends on which aspect you want to foreground: the medium (browser), the channel (web), or the lineage (net art).

How artists actually use the browser

Browser-based practice tends to fall into a few recognizable approaches. These are not strict categories, and many artists mix them.

Generative and procedural work

The artist writes rules, and the work produces variation each time it runs. Abstract animations, particle systems, and algorithmic drawings are common. The appeal is that the piece is never fixed; the code is the score, and the browser is the performer.

Interactive and responsive work

The viewer's actions complete the piece. Moving the mouse might distort a form, scrolling might reveal a narrative, or holding a key might change the sound. Here the browser's event model (clicks, movement, timing) is the artistic instrument.

Experimental video and animation in the browser

Video and animation are often embedded in browser-based work rather than presented as standalone files. The browser allows layering, real-time compositing, and interaction with moving image, which is difficult to achieve in a conventional player. This is where browser-based practice connects closely to experimental video and animation traditions.

Data-driven and networked work

Some pieces pull from live sources, APIs, or user input, so the work reflects conditions outside itself. The browser becomes a window onto a system rather than a self-contained object.

What to consider when viewing or presenting browser-based art

If you are encountering this work for the first time, a few practical points help.

Viewing

• Use a current browser; older engines may render differently or fail.
• Try the piece more than once. Generative and interactive works often reveal themselves over time.
• Interact deliberately: move the cursor, scroll, resize the window, wait. Many works reward patience.
• Expect variation. Two visits may not look the same, and that is usually intentional.

Presenting or exhibiting

• Decide whether the work is shown on a personal device, a kiosk, or a projection. Each changes the scale and the social context.
• Document with video or screen capture, not only stills, so the behavior is preserved.
• Note the browser and version used, since rendering can differ.
• Consider whether the work needs a stable connection or can run offline.

Archiving Browser-based work is fragile. Browsers update, plugins disappear, and servers go offline. Good documentation includes the code, a recorded walkthrough, and notes on the intended environment. This is a known challenge in net art and digital preservation generally.

Why the term matters

Calling a work "browser based" is a claim about where its meaning lives. It says the piece is not a picture of something, but a set of behaviors that unfold in a specific software environment. That framing helps viewers, curators, and writers treat the work on its own terms: as code, interaction, and time rather than as a static image. It also connects contemporary practice to a longer lineage of net art, experimental video, and abstraction, where artists have long treated tools and systems as creative material rather than neutral containers.

If you are new to this area, the most useful next step is simply to open a few browser-based works and spend time with them. Notice what changes, what responds to you, and what stays the same. That experience will teach you more about the medium than any definition.