Preview HTML, Markdown and CSV Files on Android
Updated November 2026. A surprising amount of website and content work still arrives as a file on a phone: an HTML email template, a Markdown note, a CSV export of leads or products. Opening those files in a generic text app often means a wall of tags or commas, with no sense of how the HTML will render or how the table is laid out. This guide shows how to preview HTML Markdown CSV on Android in one official viewer, using Dev Browser, a free Android app by My Advisers, also on Google Play.
The official product materials state that the code viewer opens HTML, CSS, JavaScript, JSON, Markdown, CSV and many other formats, and flags common errors. Officially, files can be opened from the phone’s file manager as well as from the web; syntax highlighting and line numbers make the source easier to read; wrap, copy and find help with long lines; HTML preview at a chosen width shows how a file renders; and Markdown and CSV preview show formatted notes and a table view of data files. Hex view is available for binary files. PHP and Python are displayed and checked, not executed. The app is a first pass, not a replacement for desktop developer tools.
Width matters when the file is HTML. This blog’s guide to testing a website’s desktop layout on an Android phone explains the official presets (390, 820, 1366, 1920 and 2560 pixels) and custom widths. An overview of the My Advisers tools is in the tools guide.
A single workflow to preview HTML Markdown CSV on Android
- Save the file to the phone from mail, chat or a download, with its real extension if you can:
.html,.mdor.csv. Then open it from the file manager in Dev Browser, as the official viewer allows. If the file is already on the web, open that URL instead. - Start with the source view. Official syntax highlighting and line numbers are there so you can see whether you received a complete file, a fragment, or a document that is actually XML, a spreadsheet saved with the wrong name, or an HTML file full of email-unsafe markup. Use find for a class name, a heading, or a column title.
- Switch to the official preview that matches the format. For HTML, use HTML preview at a chosen width. For Markdown, use the formatted-notes preview. For CSV, use the table view. Do not judge a CSV by how it wraps in a plain text pane, and do not judge an HTML email template only at one width.
- Run the official error check if the file is code or markup — unclosed or mismatched HTML tags, missing alt text, duplicate IDs, invalid JSON, and the other officially listed flags — then go back to the preview to see whether a fix changed the render. An error check and a preview are complementary; neither replaces the other.
- Copy, share or go back to a computer when the first pass has shown a problem worth a proper edit. Officially, the app can also help with PDF, print and share on web pages; for a local file, keep a clear copy of what you changed.
HTML preview at a chosen width
Officially, HTML preview at a chosen width shows how a file renders, which is handy for a snippet or a template someone sent you. That is different from opening a live website and stretching a viewport, although you will use the same official width presets when the question is “does this template collapse at 390 pixels, and does it still make sense at 1366?”
A useful HTML pass on a phone looks like this:
- Preview at 390 pixels. Check that headings, buttons and tables do not overflow, that images are not wider than the screen, and that navigation is still usable.
- Preview at 820 and 1366 pixels if the template is meant to be read on a tablet or a laptop, including marketing emails that many people will open on a phone anyway.
- Look at the source if a block is missing: an unclosed tag, flagged by the official error check, is a common reason a section disappears or a style “leaks” into the next block.
- Remember that a local HTML file may not load remote CSS, fonts or images the same way a live site does, depending on how those assets are referenced. A broken image in the preview may be a path problem, not a missing
<img>tag. Note it, and confirm on the live site or on a desktop when the file is part of a larger project.
The preview is a render of the file you opened. It is not a full browser-compatibility lab, and it is not a substitute for sending a real test email if the file is a mail template. It answers the first question: does this markup produce the layout I expect at this width, on this phone?
Markdown preview for notes and drafts
Officially, Markdown preview shows formatted notes. That is the right first pass when a colleague sends a README, a change log, or a draft post in Markdown rather than in a Word file. Read the formatted view for structure — headings, lists, links, and whether a code block is actually closed — then use the source view if a heading has gone wrong or a list has collapsed into a paragraph.
Markdown dialects differ. A preview that follows one common flavour may not treat every GitHub-style or table extension the same way as your publishing system. If the formatted view and your later CMS disagree, trust the CMS for the published result, and use the phone preview as a readability check, not as a certification of the dialect. The official viewer is still much faster than counting hashes in a plain-text app on a train.
CSV preview as a table
Officially, CSV preview shows a table view of data files. That is the point of opening a CSV on a phone at all. A typical export — leads, products, a rate sheet — is unreadable as one long line or as wrapped commas. In the table view you can check whether:
- the first row is a header, and the header names are the ones you expected;
- a field that contains a comma was quoted, or has split into an extra column;
- rows are truncated at the end of a download;
- empty columns or repeated headers suggest the export was run twice or saved from a sheet with extra cells.
A CSV table preview is not a spreadsheet. It will not, on the official description, replace Excel or Google Sheets for pivot tables, types, or a cleaned import. It tells you whether the file is even a table, and whether it is the table you asked for, before you forward it or import it. If the file is actually semicolon-separated, or is encoded in a way the preview does not expect, you will see broken columns; stop and open a correct export rather than editing blindly on the phone.
Treat a CSV of leads or payments as personal data, even in a preview. Do not screenshot a column of phone numbers into a public chat.
When to stay in source view, or use hex view
Syntax highlighting is the right view when you are looking for a typo, a class name, or a formula in a small snippet. Official wrap, copy and find are the tools for that job. Hex view, officially available for binary files, is a last resort when the “CSV” or “HTML” you received is not text at all — a .xlsx renamed by mistake, an image, or a truncated binary attachment. If hex view is what you need to recognise that the file is not text, stop and ask for a real CSV or HTML export. Do not try to edit raw bytes on a phone as a content workflow.
PHP and Python, officially, are displayed and checked, not executed. The same spirit applies here: preview and first-pass checks are for reading and catching obvious defects, not for running a backend.
A short example of the three previews in one afternoon
Suppose a client sends three attachments: a landing-page snippet (hero.html), a notes file (changes.md), and a product list (products.csv). Open the HTML and preview it at 390 and 1366 pixels; if a heading and a button overlap at 390, inspect the source and look for a width written in pixels that the official error check will not, by itself, call a “bug.” Open the Markdown and read the formatted notes to see whether the change list matches what you were told on the call. Open the CSV as a table and confirm there are, say, a header plus the number of rows the client claimed, with no split columns. That is a complete first pass, on the phone, before you sit down at a computer to edit. If any one of the three files is the wrong type or is truncated, you can ask for a fresh copy the same hour, rather than discovering it the next morning.
Choosing the wrong preview, and how to recover
The most common first-pass mistake is to open all three kinds of file as plain source and try to “see” them. A Markdown draft full of hashes looks unfinished when it would have been readable in the official formatted preview. A CSV of twenty columns looks like noise until the official table view is on. An HTML snippet looks like a wall of tags until you preview it at 390 pixels and notice that a button is off-screen. Use the preview that matches the extension, then go back to source only to fix something you actually saw.
The opposite mistake is to trust a preview so much that you never open the source. A Markdown preview can make a broken link look like a styled sentence. A CSV table can hide a quoted comma if you only glance at the first rows. An HTML preview can look acceptable at 1366 pixels and collapse at 390. The official workflow in this article is therefore two-step on purpose: source for completeness and for the error check, preview for meaning and for layout. If the two disagree, believe that there is a problem, and do not publish until you know which view is telling the truth.
When a file will not open as you expect, check the extension and the first bytes. A spreadsheet saved as .xlsx and renamed to .csv is not a CSV; official hex view can help you recognise a binary Office file. A Word document pasted into a .md file may contain smart quotes and images that a simple Markdown preview will not render as the sender saw them in Word. Ask for a real Markdown or HTML export rather than spending the evening decoding a hybrid file on a phone.
Frequently asked questions
Can Dev Browser preview Markdown and CSV, not only HTML?
Yes. Officially, Markdown and CSV preview show formatted notes and a table view of data files, and the viewer also opens HTML, CSS, JavaScript, JSON and many other formats.
Does HTML preview use the same widths as site testing?
You choose a width for the HTML preview, and the app’s official width presets are 390, 820, 1366, 1920 and 2560 pixels, plus custom widths. Use the same numbers so a snippet and a live page are talked about in the same language.
Will a local HTML file look exactly like the live site?
Not always. Remote assets, login state and server-side rendering may be missing. Treat the preview as a first look at the markup you were sent.
Can the CSV preview replace a spreadsheet?
No. It is a table view for a first check, not a full spreadsheet or CRM import tool.
Does this replace desktop developer tools?
No. Officially it is a complement, not a replacement. The phone pass is there so obvious problems are found where the file arrived.
Disclaimer
This article explains officially listed Dev Browser viewer and preview features. It is not a certification of layout, accessibility, validity, or data quality, and it is not a substitute for desktop tools, a spreadsheet, or a mail-testing service. Feature names can change; confirm them on the official product page. Treat files that contain personal data with care.
References
- My Advisers, Dev Browser product page: https://myadvisers.in/dev-browser/.
- MDN Web Docs, HTML: A good basis for accessibility and structure (for judging whether a template’s markup is even complete): https://developer.mozilla.org/en-US/docs/Web/HTML.
- Google Play, Dev Browser: https://play.google.com/store/apps/details?id=com.myadvisers.devbrowser.
Comments
Post a Comment