Skip to main content
Apply for a Cheap Website
Website explainer · 1:47

Frontend vs Backend: Which Part of a Website Does What?

What do developers mean by frontend and backend? They describe different parts of how a website works.

Jersey Web video: Browser side. Server side.

1:47 · No narration: the video shows each step as text on screen, and every step is written out below, with buttons that jump the video to it.

Download the on-screen text track (VTT)

The six points in the video

This is a silent video. The headings, explanations and labels below reproduce the information on screen.

  1. Step 1: The frontend meets the visitor

    The browser presents the page and its controls.

    On-screen labels: Page layout; Visible content; Visitor interaction.

  2. Step 2: The browser sends requests

    Opening a page or submitting a form can contact a server.

    On-screen labels: Requested address; Submitted information; Network connection.

  3. Step 3: The backend processes the task

    Server-side code can check a request and apply business rules.

    On-screen labels: Request checks; Business logic; Authorised action.

  4. Step 4: Stored data may be involved

    A database can hold content, accounts or order records.

    On-screen labels: Stored records; Data lookup; Approved updates.

  5. Step 5: A response returns to the browser

    The frontend can show a page, result or error message.

    On-screen labels: Returned response; Visible result; Clear feedback.

  6. Step 6: Test both sides together

    A good-looking button still needs a working action behind it.

    On-screen labels: Usable control; Successful processing; Correct final result.

A practical check for your business

Trace a sample enquiry from the browser interface to the system that processes it. Confirm where validation, storage, access checks and customer feedback happen, and who maintains those parts.

Sources and further detail

See it in a diagram

Request-response diagram showing browser controls sending a request to server-side logic, then a response returning to the browser.
Frontend and backend, explained. The browser presents the interface; the server processes supported requests and returns responses.
Read the diagram as text
  1. Browser interface: The visitor starts a task
  2. Server-side logic: The request is processed
  3. Browser feedback: The response is displayed

Test the whole journey. A visible control needs a working result behind it.

Stored records may also be involved in the task.

Diagram by Jersey Web. Open full size · Source and further detail (opens in a new tab)

Common questions

What do developers mean by frontend and backend?

They describe different parts of how a website works. Check the whole journey when something breaks.

Go further

Guide Read the practical guide More context for planning and maintaining your business website. 5 min read → Jargon Buster Frontend explained Read the related Jargon Buster explanation. Read the explanation → Jargon Buster Backend explained Read the related Jargon Buster explanation. Read the explanation →

Check the whole journey when something breaks.

Tell Jersey Web what your website needs to do and which part you want help with.

Talk to Jersey Web →

More video tips

All 205 videos →
Length 1:47 Account security

Website Databases Explained: Content, Records and Recovery

Website databases, explained.
Length 1:47 Account security

Website Cookies Explained: Sessions, Preferences and Tracking

Small pieces of browser data.
Length 1:47 Website connections

Browser Storage Explained: Local Storage and Session Storage

Local and session storage.